Triple
T5035762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tallboy bomb |
E113415
|
entity |
| Predicate | operationalAltitude |
P60638
|
FINISHED |
| Object | dropped from high altitude |
—
|
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: dropped from high altitude | Statement: [Tallboy bomb, operationalAltitude, dropped from high altitude]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationalAltitude Context triple: [Tallboy bomb, operationalAltitude, dropped from high altitude]
-
A.
locatedAtAltitude
Indicates that an entity exists or is positioned at a specific height above a reference level, typically sea level.
-
B.
altitudeCapability
Indicates the maximum or typical altitude at which an entity can effectively operate or function.
-
C.
altitudeOfRecordFlight
Indicates the altitude reached during a particular record-setting flight.
-
D.
flightLevelRange
Indicates the range of permissible or actual flight levels associated with an aircraft’s operation or a specific flight segment.
-
E.
operationalCeiling
Indicates the maximum altitude at which an entity (such as an aircraft or system) is designed or permitted to operate effectively and safely.
- 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_69bd44384298819089c49e7c330ec7b8 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73b9ad488190a2a8c4da8858eb91 |
completed | March 20, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_69bd71509e9c8190a60c1d8d04936a12 |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd724ff2b4819091351cf80d3647a1 |
completed | March 20, 2026, 4:14 p.m. |
Created at: March 20, 2026, 1:36 p.m.