Triple
T23080481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lipschitz condition |
E575454
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regularity condition |
C17827
|
CONCEPT FINISHED |
How this triple was built (1 step)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: regularity condition Context triple: [Lipschitz condition, instanceOf, regularity condition]
-
A.
integrability condition
An integrability condition is a mathematical requirement, often expressed as a compatibility or consistency relation among derivatives, that ensures a given system of equations or differential forms admits a solution or can be derived from a potential function.
-
B.
boundary condition
A boundary condition specifies the behavior or constraints imposed on the edges or limits of a system, domain, or problem space to ensure a well-defined and solvable model.
-
C.
regulatory provision
A regulatory provision is a specific, authoritative rule or requirement established by a regulatory body to govern conduct, processes, or standards within a defined domain.
-
D.
formal condition set
chosen
A formal condition set is a precisely defined collection of criteria or constraints that must be satisfied for a system, process, or statement to be considered valid or applicable.
-
E.
radiation condition
A radiation condition is a mathematical requirement imposed on solutions of wave or field equations to ensure that energy propagates outward from sources and no unphysical incoming waves appear at infinity.
- F. None of above.
Provenance (1 batch)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69e245be28d48190ad1348d5a73db37d |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:56 p.m.