Triple
T35420308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BMW 435i Gran Coupé |
E1023764
|
entity |
| Predicate | hasBodyDesignation |
P151201
|
FINISHED |
| Object | Gran Coupé |
—
|
NE NERFINISHED |
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: Gran Coupé | Statement: [BMW 435i Gran Coupé, hasBodyDesignation, Gran Coupé]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBodyDesignation Context triple: [BMW 435i Gran Coupé, hasBodyDesignation, Gran Coupé]
-
A.
hasBodyManufacturer
Indicates that an entity has a specific manufacturer responsible for producing its body or main physical structure.
-
B.
hasBodyColor
Indicates that an entity possesses a particular body color as one of its attributes.
-
C.
hasFullCarDesignation
chosen
Indicates that an entity is associated with a complete, formal car designation (such as full model name or code) rather than a partial or abbreviated identifier.
-
D.
hasBodyPlanFeature
Indicates that an organism’s body plan includes a specific structural or morphological feature.
-
E.
hasBodyName
Indicates that an entity has a specific name assigned to its physical body.
- 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_69f76df6704081909900c60be10d5849 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fdd2be648c8190b60b3d1caeb44364 |
completed | May 8, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69fdd14a5c708190a6f95ec61f4fc28f |
completed | May 8, 2026, 12:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.