Triple
T28826855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SEAT Toledo |
E727930
|
entity |
| Predicate | fourthGenerationBodyStyle |
P66190
|
FINISHED |
| Object | 4-door sedan with liftback trunk |
—
|
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: 4-door sedan with liftback trunk | Statement: [SEAT Toledo, fourthGenerationBodyStyle, 4-door sedan with liftback trunk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fourthGenerationBodyStyle Context triple: [SEAT Toledo, fourthGenerationBodyStyle, 4-door sedan with liftback trunk]
-
A.
thirdGenerationBodyStyle
Indicates that the subject has the body style corresponding to the third generation of a particular model or design series.
-
B.
carBodyStyle
chosen
Indicates the specific body configuration or design style that characterizes a car (e.g., sedan, hatchback, SUV).
-
C.
oreBodyStyle
Indicates the specific body style or physical form that an ore or mineral deposit exhibits.
-
D.
fourthGeneration
Indicates that one entity is in the fourth generation of descent or succession relative to another entity.
-
E.
bodyTypes
Indicates a relationship where one or more body types are associated with or assigned to an 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f67f7efc3c8190986d2d95b7a23729 |
completed | May 2, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 28, 2026, 6:36 a.m.