Triple
T10293977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford Falcon platform |
E241434
|
entity |
| Predicate | bodyStyleCompatibility |
P74532
|
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: [Ford Falcon platform, bodyStyleCompatibility, sedan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyStyleCompatibility Context triple: [Ford Falcon platform, bodyStyleCompatibility, sedan]
-
A.
layoutCompatibility
Indicates that two layouts can coexist or be used interchangeably without causing conflicts or usability issues.
-
B.
bodyStyleProduced
Indicates that a particular body style was manufactured or produced by a given entity (such as a company, plant, or production line).
-
C.
bodyStyleCategory
chosen
Indicates the general body style classification or category that an item (such as a vehicle or product) belongs to.
-
D.
compatibilityModel
Indicates that one entity is defined or evaluated according to a specific compatibility framework, standard, or model in relation to another entity.
-
E.
bodyStyleHistory
Indicates the historical record of changes or versions in an entity’s body style over time.
- 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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2d46fb08190b7694290692e47dc |
completed | April 7, 2026, 9:48 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f35e548190be3b4d92d65d2d20 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:42 a.m.