Triple
T35887089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Audi Brussels plant |
E1037677
|
entity |
| Predicate | startOfProductionOfAudiETron |
P31468
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Audi Brussels plant, startOfProductionOfAudiETron, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOfProductionOfAudiETron Context triple: [Audi Brussels plant, startOfProductionOfAudiETron, 2018]
-
A.
startDateAsAudiPlant
Indicates the date on which something begins operating or is established specifically as an Audi plant.
-
B.
enteredAutomobileProduction
Indicates that an entity began manufacturing automobiles as a commercial or industrial activity.
-
C.
beganCommercialProduction
Indicates that an entity started producing something commercially, marking the commencement of its large-scale or market-oriented production.
-
D.
massProductionStart
chosen
Indicates the point in time when an item or product begins to be manufactured at large scale in a mass-production process.
-
E.
initialProductionEndDate
Indicates the date on which the initial phase or run of production for something comes to an end.
- 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_69f76e1f4d748190bb55594d8441d70e |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a008e29f76881908e656dbbd7fceea3 |
completed | May 10, 2026, 1:54 p.m. |
| PD | Predicate disambiguation | batch_6a008dc01b308190bc26e69814692f82 |
completed | May 10, 2026, 1:53 p.m. |
Created at: May 3, 2026, 4:06 p.m.