Triple
T8119343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | small-gain theorem |
E189566
|
entity |
| Predicate | conditionType |
P35662
|
FINISHED |
| Object | sufficient condition |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: sufficient condition | Statement: [small-gain theorem, conditionType, sufficient condition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conditionType Context triple: [small-gain theorem, conditionType, sufficient condition]
-
A.
typeOfCondition
chosen
Indicates that one condition is a specific kind, category, or subtype of another condition.
-
B.
equalityCondition
Indicates that two values, expressions, or attributes must be exactly the same for the condition to be satisfied.
-
C.
coreCondition
Indicates that something serves as the primary or fundamental condition that must hold for a situation, process, or relationship to apply.
-
D.
conditions
Indicates that one entity specifies or imposes requirements, constraints, or circumstances that must be satisfied or hold true for another entity or situation.
-
E.
variableCondition
Indicates that a variable is subject to a specific state, constraint, or requirement that must hold for a given context or operation.
- F. None of above.
Provenance (3 batches)
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_69ca82baad008190ab2859712b9b1607 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4664fef881908b0dc7b158aca398 |
completed | March 31, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69cb368e7f4c81909aabd7716f0de79d |
completed | March 31, 2026, 2:50 a.m. |
Created at: March 30, 2026, 5:33 p.m.