Triple
T36838771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deutsche Telekom AG |
E910345
|
entity |
| Predicate | tradingSymbolOnXetra |
P1447
|
FINISHED |
| Object | DTE |
—
|
NE NERFINISHED |
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: DTE | Statement: [Deutsche Telekom AG, tradingSymbolOnXetra, DTE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradingSymbolOnXetra Context triple: [Deutsche Telekom AG, tradingSymbolOnXetra, DTE]
-
A.
isExchangeTraded
Indicates that the entity is traded on a formal exchange or marketplace rather than over-the-counter or privately.
-
B.
identifiesTradingVenue
Indicates that one entity specifies or designates the trading venue associated with another entity or transaction.
-
C.
isElectronicTradingSymbol
Indicates that one entity is the electronic trading symbol (e.g., ticker used in electronic markets) associated with another entity.
-
D.
underlyingExchangeMIC
Indicates the Market Identifier Code (MIC) of the exchange on which the referenced instrument or trade is fundamentally listed or executed.
-
E.
tickerSymbol
chosen
Indicates the association between a financial instrument or company and its unique abbreviated code used for trading on a securities exchange.
- 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_69f76e7f65a881908651b702da592b6d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffaa7bc45c8190b907db8579244a7b |
completed | May 9, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69ffa9f6c9a481908fbd4d18b311cbe2 |
completed | May 9, 2026, 9:41 p.m. |
Created at: May 3, 2026, 4:13 p.m.