Triple
T35420307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BMW 435i Gran Coupé |
E1023764
|
entity |
| Predicate | hasTrimDesignation |
P200850
|
FINISHED |
| Object | 435i |
—
|
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: 435i | Statement: [BMW 435i Gran Coupé, hasTrimDesignation, 435i]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrimDesignation Context triple: [BMW 435i Gran Coupé, hasTrimDesignation, 435i]
-
A.
hasTrimMaterial
Indicates that one entity uses or features a particular material specifically for its trim or edging components.
-
B.
hasColumbiaNameOnTrim
Indicates that an object features the Columbia brand name printed or displayed on its trim.
-
C.
hasFullCarDesignation
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.
hasPadDesignation
Indicates that an entity is assigned or associated with a specific pad identifier or designation.
-
E.
hasInternalDesignationFor
Indicates that one entity assigns or uses an internal label, code, or designation to refer to another entity.
- 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_69f76df6704081909900c60be10d5849 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffb1f0b03c81909ddb81f07ce74e88 |
completed | May 9, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69ffb1662b2481908582e0612744f4c5 |
completed | May 9, 2026, 10:12 p.m. |
| PDg | Predicate description generation | batch_69ffb1f001948190a63c493b596a97b9 |
completed | May 9, 2026, 10:15 p.m. |
Created at: May 3, 2026, 4:03 p.m.