Triple
T14040862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BMW E89 |
E337839
|
entity |
| Predicate | chassisCode |
P44383
|
FINISHED |
| Object | E89 |
E337839
|
NE 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: E89 | Statement: [BMW E89, chassisCode, E89]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: E89 Context triple: [BMW E89, chassisCode, E89]
-
A.
E89
chosen
E89 is the internal BMW designation for the second-generation Z4 roadster, known for its retractable hardtop and sporty grand-touring character.
-
B.
E81
E81 is a major north–south European route that runs through parts of Romania and other Eastern European countries, connecting key cities and facilitating international road transport.
-
C.
E80
E80 is a major European route that forms part of the international road network connecting Podgorica with other key cities across the continent.
-
D.
EH8
EH8 is a central Edinburgh postcode district covering areas including Holyrood and parts of the city’s historic core.
-
E.
E75
The E75 is a Nokia Eseries smartphone known for its slide-out QWERTY keyboard and business-oriented features.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d81c664e48819088cbd8f433aeffe5 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de311814e48190adb637e1c97c0658 |
completed | April 14, 2026, 12:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fbc33dbc8c819080b6cb3d589da7a1 |
completed | May 6, 2026, 10:39 p.m. |
Created at: April 9, 2026, 10:20 p.m.