Triple
T35519824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TX60 |
E1026521
|
entity |
| Predicate | underlyingIndexName |
P5158
|
FINISHED |
| Object | S&P/TSX 60 Index |
—
|
NE NERFINISHED |
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: S&P/TSX 60 Index | Statement: [TX60, underlyingIndexName, S&P/TSX 60 Index]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underlyingIndexName Context triple: [TX60, underlyingIndexName, S&P/TSX 60 Index]
-
A.
associatedIndex
chosen
Indicates that one entity is linked to another through a corresponding index or positional reference.
-
B.
indexUsedBy
Indicates that a particular index is utilized or referenced by another entity, such as a query, process, or data structure.
-
C.
underlyingRelation
Indicates that one entity serves as a fundamental basis, cause, or support for another entity or relationship.
-
D.
coreIndex
Indicates the position or identifier of an entity within a central or primary ordered structure (its core sequence or index).
-
E.
otherIndex
Indicates that one entity is associated with a different or alternative index position relative to another entity or reference point.
- 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_69f76dfe78b081908e2b14cb88dd8c00 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
Created at: May 3, 2026, 4:04 p.m.