Triple
T9525894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dambuster bomb |
E229758
|
entity |
| Predicate | deliveryAltitude |
P60638
|
FINISHED |
| Object | about 60 feet above water |
—
|
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: about 60 feet above water | Statement: [Dambuster bomb, deliveryAltitude, about 60 feet above water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deliveryAltitude Context triple: [Dambuster bomb, deliveryAltitude, about 60 feet above water]
-
A.
locatedAtAltitude
Indicates that an entity exists or is positioned at a specific height above a reference level, typically sea level.
-
B.
operationalAltitude
chosen
Indicates the typical or designated altitude at which an entity is intended to operate.
-
C.
aircraftHeight
Indicates the vertical distance or altitude of an aircraft relative to a reference level (such as ground or sea level).
-
D.
hasAltitudeFeature
Indicates that an entity possesses a characteristic or attribute related to its elevation or vertical position above a reference level.
-
E.
altitudeOfRecordFlight
Indicates the altitude reached during a particular record-setting flight.
- 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_69ca847870a881909d8d751a7d29da39 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd989b529c81909ee18dd3d468c816 |
completed | April 1, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cca56a3d088190bdc16670678fb6c6 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:59 p.m.