Triple
T5368805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peugeot 5008 |
E108793
|
entity |
| Predicate | successorToBodyStyle |
P3901
|
FINISHED |
| Object | Peugeot 5008 MPV succeeded by Peugeot 5008 SUV |
—
|
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: Peugeot 5008 MPV succeeded by Peugeot 5008 SUV | Statement: [Peugeot 5008, successorToBodyStyle, Peugeot 5008 MPV succeeded by Peugeot 5008 SUV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorToBodyStyle Context triple: [Peugeot 5008, successorToBodyStyle, Peugeot 5008 MPV succeeded by Peugeot 5008 SUV]
-
A.
secondGenerationBodyStyle
Indicates that the subject has or is associated with the second generation of a particular body style.
-
B.
successorBody
chosen
Indicates that one body or entity directly follows and replaces another in a sequence or succession.
-
C.
thirdGenerationBodyStyle
Indicates that the subject has the body style corresponding to the third generation of a particular model or design series.
-
D.
replacedBodyType
Indicates that one body type has been substituted or superseded by another body type.
-
E.
successorTractionType
Indicates that one traction type directly follows or replaces another in a sequence or evolution of traction systems.
- 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_69bd440c77948190aad2a5f39b7b80f5 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd86856f688190a34ab93619bae134 |
completed | March 20, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69bd845f41f88190b75b8b64b9e41862 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:02 p.m.