Triple
T26024576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BMW IIIa |
E647253
|
entity |
| Predicate | altitudeOptimization |
P160315
|
FINISHED |
| Object | optimized for operation above 3000 meters |
—
|
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: optimized for operation above 3000 meters | Statement: [BMW IIIa, altitudeOptimization, optimized for operation above 3000 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: altitudeOptimization Context triple: [BMW IIIa, altitudeOptimization, optimized for operation above 3000 meters]
-
A.
altitudeEffect
Indicates how a change in altitude influences or modifies some property, condition, or outcome.
-
B.
highestPassApproxElevation
Indicates the approximate elevation of the highest pass along a given route or within a specified area.
-
C.
meetsAtAltitude
Indicates that two or more entities come together or intersect at a specific vertical height or elevation.
-
D.
altitudeProfile
Indicates the variation of elevation or height along a path, route, or trajectory over distance or time.
-
E.
altitudeRole
Indicates the role or function an entity has with respect to altitude, such as how it is used, classified, or interpreted in terms of vertical position or height.
- F. None of above. chosen
Provenance (4 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_69e77e8b60e88190a3b26c4f0032a2c2 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f605ea27648190b481ce5a9c0aef22 |
completed | May 2, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f600be0de88190989611e952b03117 |
completed | May 2, 2026, 1:48 p.m. |
Created at: April 22, 2026, 9:05 a.m.