Triple
T8929229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TDI engines |
E212609
|
entity |
| Predicate | brand |
P1500
|
FINISHED |
| Object | TDI |
E212609
|
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: TDI | Statement: [TDI engines, brand, TDI]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TDI Context triple: [TDI engines, brand, TDI]
-
A.
TDI
TDI (Test Data In) is the serial input pin used in JTAG boundary-scan to feed test instructions and data into a device’s test access port.
-
B.
TDI engines
chosen
TDI engines are Audi’s turbocharged direct-injection diesel powerplants known for combining strong torque with relatively high fuel efficiency.
-
C.
TD
TD is the stock ticker symbol for The Toronto-Dominion Bank, one of Canada’s largest multinational banking and financial services institutions.
-
D.
TD
TD is the two-letter ISO 3166-1 alpha-2 country code assigned to Chad.
-
E.
TD
TD is a UK postcode area covering parts of the Scottish Borders and northern England, including towns such as Galashiels and Berwick-upon-Tweed.
- 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_69ca8395c438819087d7cb844ab5990c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc667470308190a75ba63de803e3a2 |
completed | April 1, 2026, 12:27 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfba5e887c8190851f2fb533653c6e |
completed | April 3, 2026, 1:02 p.m. |
Created at: March 30, 2026, 6:57 p.m.