Triple
T25073702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euler class |
E627991
|
entity |
| Predicate | isZeroIf |
P157613
|
FINISHED |
| Object | bundle admits a nowhere-vanishing section |
—
|
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: bundle admits a nowhere-vanishing section | Statement: [Euler class, isZeroIf, bundle admits a nowhere-vanishing section]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isZeroIf Context triple: [Euler class, isZeroIf, bundle admits a nowhere-vanishing section]
-
A.
isZeroFor
Indicates that a given value, expression, or function evaluates to zero when applied to or considered with respect to a specified entity or context.
-
B.
isNonZeroBecause
Indicates that a value is non-zero specifically due to the stated cause, reason, or contributing factor.
-
C.
isNonzeroFor
Indicates that a given value, function, or quantity is not equal to zero under specified conditions or for specified inputs.
-
D.
conditionOnZeros
Indicates that one entity’s state, behavior, or validity depends specifically on the presence, position, or pattern of zero values in another entity.
-
E.
isZeroConfiguration
Indicates that something requires no manual setup or configuration to function correctly.
- F. None of above. chosen
Provenance (4 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f45d177c3881909ac5058e3e866d93 |
completed | May 1, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
| PDg | Predicate description generation | batch_69f448fe11f08190bdd53ca7ba2d51e4 |
completed | May 1, 2026, 6:32 a.m. |
Created at: April 18, 2026, 6:20 a.m.