Triple
T10908673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lincoln division of Ford Motor Company |
E257634
|
entity |
| Predicate | vehicleBodyStyleOffered |
P51843
|
FINISHED |
| Object | 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: SUV | Statement: [Lincoln division of Ford Motor Company, vehicleBodyStyleOffered, SUV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vehicleBodyStyleOffered Context triple: [Lincoln division of Ford Motor Company, vehicleBodyStyleOffered, SUV]
-
A.
carBodyStyle
Indicates the specific body configuration or design style that characterizes a car (e.g., sedan, hatchback, SUV).
-
B.
offersBodyStyle
chosen
Indicates that an entity (such as a manufacturer or model line) makes a particular vehicle body style available as an option.
-
C.
carbodyMaterial
Indicates the material from which a vehicle’s body or main structural shell is made.
-
D.
hasExteriorStyle
Indicates that an entity possesses or is characterized by a particular exterior design or stylistic appearance.
-
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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7706824d08190ba894d144cc6b3ba |
completed | April 9, 2026, 9:24 a.m. |
| PD | Predicate disambiguation | batch_69d70d3d69e08190bb369e9a7927142c |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:22 p.m.