Triple
T24269643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S&P Global Broad Market Index Series |
E605240
|
entity |
| Predicate | includesIndexType |
P73661
|
FINISHED |
| Object | price return 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: price return indices | Statement: [S&P Global Broad Market Index Series, includesIndexType, price return indices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesIndexType Context triple: [S&P Global Broad Market Index Series, includesIndexType, price return indices]
-
A.
requiresIndicesType
Indicates that one entity depends on or mandates a specific type or format of indices from another entity in order to function or be valid.
-
B.
indexType
Indicates the classification or category of an index associated with an entity or structure.
-
C.
hasIndexType
chosen
Indicates that an entity is associated with a particular type or category of index used to organize, reference, or access it.
-
D.
indexTypeMustConformTo
Indicates that the type used as an index in a construct must satisfy or conform to a specified constraint or protocol.
-
E.
allowsIndexInclusion
Indicates that one entity permits another entity to be included or listed within an index or indexing system.
- 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_69e2954707dc8190915551eb114cfff6 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28d58666881909f28f4d4f0f7d590 |
completed | April 29, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:07 a.m.