Triple
T15790680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Audi A6 e-tron |
E382855
|
entity |
| Predicate | previewsModelLine |
P27119
|
FINISHED |
| Object | future Audi A6 electric production models |
—
|
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: future Audi A6 electric production models | Statement: [Audi A6 e-tron, previewsModelLine, future Audi A6 electric production models]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previewsModelLine Context triple: [Audi A6 e-tron, previewsModelLine, future Audi A6 electric production models]
-
A.
firstModelLineOf
Indicates that one entity is the first line of a model or modeling construct associated with another entity.
-
B.
hasModelLine
chosen
Indicates that an item, product, or entity belongs to or is associated with a particular model line or series.
-
C.
producedModel
Indicates that one entity created, manufactured, or generated the other entity as a model or product.
-
D.
productLineStart
Indicates the point in time or position at which a particular product line begins or is first introduced.
-
E.
firstModel
Indicates that an entity is the initial or earliest model/version in a sequence or series of models.
- 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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4d819c881908bc43a6124a1bb2e |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e00537bd1c81908d6e832792fd934f |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:48 a.m.