Triple
T1381114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SPX |
E29338
|
entity |
| Predicate | underlyingType |
P24894
|
FINISHED |
| Object | broad-based index |
—
|
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: broad-based index | Statement: [SPX, underlyingType, broad-based index]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underlyingType Context triple: [SPX, underlyingType, broad-based index]
-
A.
originalType
Indicates that one entity represents the initial or source type from which another entity is derived, transformed, or reclassified.
-
B.
underlies
Indicates that one entity serves as a fundamental basis, support, or underlying cause for another entity, condition, or phenomenon.
-
C.
invariantType
Indicates that one entity has a type or classification that remains constant or unchanged under specified conditions or transformations.
-
D.
basedUnitType
Indicates that one unit is defined or derived in terms of another underlying (base) unit type.
-
E.
parentType
chosen
Indicates that one entity serves as the direct parent or higher-level type from which another entity is derived or classified.
- 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_69a498d883a48190bfdca525296ef7ee |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c31b176c8190a896183140c5c8be |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4befe343c81909f758440a531b5be |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.