Triple
T30791032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Audi S6 |
E784094
|
entity |
| Predicate | thirdGenerationBasedOn |
P181763
|
FINISHED |
| Object | C6 platform |
—
|
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: C6 platform | Statement: [Audi S6, thirdGenerationBasedOn, C6 platform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdGenerationBasedOn Context triple: [Audi S6, thirdGenerationBasedOn, C6 platform]
-
A.
thirdGeneration
Indicates that one entity is the grandchild (third generation) relative to another entity in a lineage or succession.
-
B.
thirdGenerationStart
Indicates the point in time or event at which the third generation of a lineage, product line, or sequence begins.
-
C.
thirdGenerationEnd
Indicates that a third generation in a sequence, lineage, or process has reached its endpoint or conclusion.
-
D.
thirdGenerationProduction
Indicates that the subject is involved in producing or manufacturing items belonging to the third generation of a product, technology, or design series.
-
E.
thirdGenerationName
Indicates that the object is the name or designation assigned to the third generation in a lineage or sequence associated with the subject.
- F. None of above. chosen
Provenance (4 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_69f224b2e2a48190b19aa43db9da5b67 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7824dc3f0819092a5102895b4a478 |
completed | May 3, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
| PDg | Predicate description generation | batch_69f7817c79e081908e685c48165e086b |
completed | May 3, 2026, 5:10 p.m. |
Created at: April 29, 2026, 8:42 p.m.