Triple
T16150916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Todd class |
E391905
|
entity |
| Predicate | degreeZeroComponent |
P97907
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Todd class, degreeZeroComponent, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: degreeZeroComponent Context triple: [Todd class, degreeZeroComponent, 1]
-
A.
degreeZeroPart
chosen
Indicates that one entity is the degree-zero (constant or base-level) component or part of another entity within a graded or hierarchical structure.
-
B.
isZeroDimensional
Indicates that the entity has zero spatial dimensions, existing as a point-like object without length, area, or volume.
-
C.
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.
-
D.
derivativeAtZero
Indicates that one quantity is the derivative (rate of change) of another quantity evaluated specifically at the point where the input equals zero.
-
E.
coordinateComponent
Indicates that one entity is a component or part of a larger coordinated structure or system involving the other entity.
- 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_69d87f1c65e48190aa2b4c472e9bafc4 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21d9724808190a8332987583a345a |
completed | April 17, 2026, 11:46 a.m. |
| PD | Predicate disambiguation | batch_69e1828abb608190a99d86bce1d77de2 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:01 a.m.