Triple
T1144097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DAX |
E23523
|
entity |
| Predicate | isBenchmarkIndex |
P5742
|
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: [DAX, isBenchmarkIndex, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBenchmarkIndex Context triple: [DAX, isBenchmarkIndex, true]
-
A.
benchmarkFor
Indicates that one entity serves as a standard or reference point against which the performance, quality, or characteristics of another entity are measured or evaluated.
-
B.
primaryBenchmarkProvider
Indicates that one entity serves as the main or default source of benchmark data or performance standards for another entity.
-
C.
isMajorIndexOf
Indicates that one entity serves as the primary or major index reference for locating, organizing, or identifying another entity.
-
D.
isPriceIndex
chosen
Indicates that a value represents a price index, expressing the relative level or change of prices compared to a reference point or period.
-
E.
hasIndex
Indicates that one entity serves as an index or positional reference for another entity within an ordered collection or structure.
- 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_69a493ef399c8190b04b9146d2314f59 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bc5008d8819095c1ffb5db5b4911 |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4d4104819084027a043c6118cb |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.