Triple
T3182050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BMW 7 Series |
E66610
|
entity |
| Predicate | typicalEngineLayout |
P19520
|
FINISHED |
| Object | inline-6 engines |
—
|
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: inline-6 engines | Statement: [BMW 7 Series, typicalEngineLayout, inline-6 engines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEngineLayout Context triple: [BMW 7 Series, typicalEngineLayout, inline-6 engines]
-
A.
typicalEngine
Indicates that an entity is the standard or commonly used engine for another entity (such as a vehicle, device, or system).
-
B.
enginePlacement
Indicates the spatial or structural position where an engine is located or mounted relative to another object or system.
-
C.
vehicleLayout
Indicates how the components or seating within a vehicle are arranged or configured relative to each other.
-
D.
propulsionLayout
chosen
Indicates how propulsion components are arranged or configured relative to each other within a system.
-
E.
wheelArrangementSystem
Indicates the specific configuration or system by which the wheels of a vehicle or rolling stock are arranged and organized.
- 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_69ad8587c1bc8190a2595f2c22ee1001 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada6bd07888190b680eace8290d821 |
completed | March 8, 2026, 4:41 p.m. |
| PD | Predicate disambiguation | batch_69ad9e02677c8190a21d93b1259b2761 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:06 p.m.