Triple
T12579656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S&P/ASX 300 |
E300299
|
entity |
| Predicate | hasTotalReturnIndex |
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: [S&P/ASX 300, hasTotalReturnIndex, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTotalReturnIndex Context triple: [S&P/ASX 300, hasTotalReturnIndex, 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.
isTotalMarketIndex
Indicates that the referenced financial instrument or dataset represents a total market index covering a broad or complete segment of a market rather than a subset.
-
C.
isTotalReturnVariantAvailable
Indicates whether a total return variant of a product, instrument, or metric is available.
-
D.
isEquityIndexTracker
Indicates that an entity tracks, replicates, or follows the performance of a specified equity (stock market) index.
-
E.
hasTotalNumber
Indicates that an entity is associated with a specific overall count or sum of items, elements, or units.
- 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_69d7bde87b648190bcd0266e9efde098 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954e6e20481908bca684c4b497c48 |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95416cbd88190b2c65196162349bc |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 5 p.m.