Triple
T3707056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercedes-Benz CLS |
E80917
|
entity |
| Predicate | primaryBodyType |
P50920
|
FINISHED |
| Object | fastback sedan |
—
|
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: fastback sedan | Statement: [Mercedes-Benz CLS, primaryBodyType, fastback sedan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryBodyType Context triple: [Mercedes-Benz CLS, primaryBodyType, fastback sedan]
-
A.
parentBodyType
Indicates that one entity has a body type that serves as the parent or base classification from which another entity's body type is derived or organized.
-
B.
typicalBodyType
Indicates that one entity is the usual or characteristic body type associated with another entity.
-
C.
residesOverBodyType
Indicates that one entity is positioned or located above another entity that is characterized by a specific body type.
-
D.
primaryBody
Indicates that one entity serves as the main or principal body associated with another entity.
-
E.
establishedBodyType
Indicates that an entity has formally created, founded, or set up a particular organizational body or structure.
- 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_69ad8b1793888190a5f70e4b21dc05a1 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adc57edd748190a006e15fa0248679 |
completed | March 8, 2026, 6:52 p.m. |
| PD | Predicate disambiguation | batch_69adc041a8608190a2d543dab6d2ef6c |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc133ef50819094c2b971f31f1615 |
completed | March 8, 2026, 6:34 p.m. |
Created at: March 8, 2026, 3:33 p.m.