Triple
T30913257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BMW E70 |
E787513
|
entity |
| Predicate | internalModelDesignation |
P75661
|
FINISHED |
| Object | E70 |
—
|
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: E70 | Statement: [BMW E70, internalModelDesignation, E70]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: internalModelDesignation Context triple: [BMW E70, internalModelDesignation, E70]
-
A.
hasInternalDesignationFor
chosen
Indicates that one entity assigns or uses an internal label, code, or designation to refer to another entity.
-
B.
manufacturerDesignation
Indicates that a specific designation, code, or model identifier has been assigned by the manufacturer to the referenced product or item.
-
C.
robotModelDesignation
Indicates the specific model identifier or designation assigned to a robot.
-
D.
systemDesignation
Indicates that an entity has been assigned a specific formal label or identifier within a defined system or framework.
-
E.
prototypeDesignation
Indicates that one entity is designated or identified as a prototype version or exemplar of another entity.
- 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_69f224be300c8190a6513ce1ee0a7026 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: April 29, 2026, 8:51 p.m.