Triple
T1144118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DAX |
E23523
|
entity |
| Predicate | hasFamilyMember |
P7844
|
FINISHED |
| Object | TecDAX |
E129619
|
NE 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: TecDAX | Statement: [DAX, hasFamilyMember, TecDAX]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TecDAX Context triple: [DAX, hasFamilyMember, TecDAX]
-
A.
TecDAX
chosen
TecDAX is a German stock market index that tracks the performance of major technology-focused companies listed in Germany.
-
B.
TEC
TEC is the commonly used acronym for the Episcopal Church, a mainline Anglican Christian denomination based in the United States.
-
C.
SDAX
SDAX is a German stock market index that tracks the performance of small-cap companies listed on the Frankfurt Stock Exchange.
-
D.
MDAX
MDAX is a German stock market index that tracks the performance of 50 mid-cap companies listed on the Frankfurt Stock Exchange.
-
E.
DAX
DAX (Data Analysis Expressions) is a formula and query language used in Microsoft Power BI, Excel Power Pivot, and Analysis Services for creating custom calculations and data models.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac5eb1f7d08190ba722dcbbc8a6799 |
completed | March 7, 2026, 5:21 p.m. |
Created at: March 1, 2026, 7:44 p.m.