Triple
T35519820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TX60 |
E1026521
|
entity |
| Predicate | underlyingIndexCategory |
P19875
|
FINISHED |
| Object | large-cap 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: large-cap index | Statement: [TX60, underlyingIndexCategory, large-cap index]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underlyingIndexCategory Context triple: [TX60, underlyingIndexCategory, large-cap index]
-
A.
associatedIndex
Indicates that one entity is linked to another through a corresponding index or positional reference.
-
B.
indexType
chosen
Indicates the classification or category of an index associated with an entity or structure.
-
C.
otherIndex
Indicates that one entity is associated with a different or alternative index position relative to another entity or reference point.
-
D.
underlyingData
Indicates that one entity serves as the foundational or source data upon which another entity is based, derived, or computed.
-
E.
coreIndex
Indicates the position or identifier of an entity within a central or primary ordered structure (its core sequence or index).
- 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_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: May 3, 2026, 4:04 p.m.