Triple
T5052011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saab Aero |
E113806
|
entity |
| Predicate | offeredWithBodyStyle |
P51843
|
FINISHED |
| Object | 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: sedan | Statement: [Saab Aero, offeredWithBodyStyle, sedan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offeredWithBodyStyle Context triple: [Saab Aero, offeredWithBodyStyle, sedan]
-
A.
offersBodyStyle
chosen
Indicates that an entity (such as a manufacturer or model line) makes a particular vehicle body style available as an option.
-
B.
hasExteriorStyle
Indicates that an entity possesses or is characterized by a particular exterior design or stylistic appearance.
-
C.
hasBodyColor
Indicates that an entity possesses a particular body color as one of its attributes.
-
D.
associatedWithBodyStyles
Indicates a relationship where something (such as a product, model, or item) is linked or connected to one or more specific body styles.
-
E.
thirdGenerationBodyStyle
Indicates that the subject has the body style corresponding to the third generation of a particular model or design series.
- 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_69bd443aa1f88190abb992d138f2cf42 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7426fc8081908a8227f73168c235 |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd715479f08190933604aebd34414f |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:37 p.m.