Triple
T14583041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BMW E32 |
E342240
|
entity |
| Predicate | topModel |
P96011
|
FINISHED |
| Object | 750iL |
E1109174
|
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: 750iL | Statement: [BMW E32, topModel, 750iL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 750iL Context triple: [BMW E32, topModel, 750iL]
-
A.
750i
chosen
The 750i is the flagship V12-powered luxury sedan variant of BMW's E32 7 Series, known for its advanced technology and high-end comfort.
-
B.
745i
The 745i is a high-performance, turbocharged flagship variant of BMW’s first-generation 7 Series (E23), produced primarily for the European market in the early 1980s.
-
C.
735iL
The 735iL is a long-wheelbase luxury sedan variant of BMW’s second-generation 7 Series (E32), offering enhanced rear passenger space and comfort.
-
D.
BMW M135i
The BMW M135i is a high-performance hot hatchback that combines a powerful turbocharged engine with sport-tuned handling and premium features.
-
E.
BMW i5
The BMW i5 is a fully electric executive sedan from BMW’s 5 Series lineup, offering premium performance, advanced technology, and zero-emission driving.
- 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_69d822ddc0f081909cd8163c7de298cd |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb41e71748190a1deacc819dd26d3 |
completed | April 14, 2026, 9:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fda9167b888190abb8f301b0c7c55b |
completed | May 8, 2026, 9:12 a.m. |
Created at: April 10, 2026, 1:24 a.m.