Triple
T1336733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nasdaq Composite Index |
E28768
|
entity |
| Predicate | isTotalReturnIndexAvailable |
P24415
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Nasdaq Composite Index, isTotalReturnIndexAvailable, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTotalReturnIndexAvailable Context triple: [Nasdaq Composite Index, isTotalReturnIndexAvailable, true]
-
A.
isTotalReturnIndex
chosen
Indicates that the index value reflects total return, including both price changes and reinvested income such as dividends or interest.
-
B.
hasTotalNumber
Indicates that an entity is associated with a specific overall count or sum of items, elements, or units.
-
C.
hasBaseIndex
Indicates that one entity serves as the reference or starting index from which another entity’s position, offset, or ordering is calculated.
-
D.
hasIndex
Indicates that one entity serves as an index or positional reference for another entity within an ordered collection or structure.
-
E.
hasTotalQuarkContent
Indicates that an entity (such as a particle or system) is associated with a specified total number or combination of quarks it contains.
- 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_69a498561a508190a3e1bc137c2b866a |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1edda1c81909a1149b254b0d57e |
completed | March 1, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69a4bef174708190a07bbc697fe19a2d |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.