Triple
T14532408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BMW E23 |
E340946
|
entity |
| Predicate | specialModel |
P19394
|
FINISHED |
| Object | 745i turbocharged variant |
—
|
LITERAL 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: 745i turbocharged variant | Statement: [BMW E23, specialModel, 745i turbocharged variant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specialModel Context triple: [BMW E23, specialModel, 745i turbocharged variant]
-
A.
possibleModel
Indicates that one entity can serve as a potential or candidate model or template for another entity.
-
B.
specialAppearance
Indicates that an entity makes a notable or exceptional appearance distinct from its usual or regular presence.
-
C.
specialValue
Indicates that an entity possesses a distinguished or exceptional value compared to typical or default values in the given context.
-
D.
hadModel
Indicates that an entity possessed, used, or was associated with a particular model (e.g., a product, design, or version) at some point in time.
-
E.
specialFeature
chosen
Indicates that an entity possesses a distinctive or noteworthy attribute, capability, or characteristic that sets it apart from others.
- 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_69d822dac79c8190a84a073f3cbaced5 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dea053f9bc8190901b9d321811d881 |
completed | April 14, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c518fc08190a6ce4d8be05c4c5d |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:22 a.m.