Triple
T30791034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Audi S6 |
E784094
|
entity |
| Predicate | fifthGenerationBasedOn |
P75506
|
FINISHED |
| Object | C8 platform |
—
|
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: C8 platform | Statement: [Audi S6, fifthGenerationBasedOn, C8 platform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fifthGenerationBasedOn Context triple: [Audi S6, fifthGenerationBasedOn, C8 platform]
-
A.
fifthGeneration
chosen
Indicates that one entity belongs to the fifth generation in a lineage, sequence, or series relative to another entity.
-
B.
fifthGenerationEnd
Indicates that a lineage, process, or sequence has reached the end of its fifth generation.
-
C.
fifthGenerationLaunch
Indicates the event or action of initiating or releasing something that belongs to its fifth generation in a series or product line.
-
D.
fifthGenerationStart
Indicates the point in time or event at which the fifth generation in a sequence, lineage, or series begins.
-
E.
fourthGeneration
Indicates that one entity is in the fourth generation of descent or succession relative to another entity.
- 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_69f224b2e2a48190b19aa43db9da5b67 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6900dbd908190baf39dd5cf37d619 |
completed | May 3, 2026, midnight |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:42 p.m.