Triple
T32017538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TDY |
E817584
|
entity |
| Predicate | associatedWithIndexFamily |
P137284
|
FINISHED |
| Object | S&P U.S. indices |
—
|
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: S&P U.S. indices | Statement: [TDY, associatedWithIndexFamily, S&P U.S. indices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithIndexFamily Context triple: [TDY, associatedWithIndexFamily, S&P U.S. indices]
-
A.
associatedIndex
Indicates that one entity is linked to another through a corresponding index or positional reference.
-
B.
associatedWithLabelFamily
Indicates that one entity is connected to or grouped with another through a shared label family or labeling category.
-
C.
baseIndexFamily
Indicates that one entity serves as the primary or reference index set upon which a family of related indexed entities is defined or organized.
-
D.
isPartOfIndexFamily
chosen
Indicates that one index belongs to, or is a member of, a larger index family or collection of related indexes.
-
E.
notableIndexFamily
Indicates that an entity is recognized as a particularly important or prominent member within a specified family group.
- 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_69f348f9e5d081908cc3f57c4942af52 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:16 a.m.