Triple
T1371629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Powers incident |
E30123
|
entity |
| Predicate | altitudeOfFlight |
P12249
|
FINISHED |
| Object | high-altitude reconnaissance level |
—
|
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: high-altitude reconnaissance level | Statement: [Powers incident, altitudeOfFlight, high-altitude reconnaissance level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: altitudeOfFlight Context triple: [Powers incident, altitudeOfFlight, high-altitude reconnaissance level]
-
A.
altitudeOfRecordFlight
chosen
Indicates the altitude reached during a particular record-setting flight.
-
B.
locatedAtAltitude
Indicates that an entity exists or is positioned at a specific height above a reference level, typically sea level.
-
C.
altitudeCapability
Indicates the maximum or typical altitude at which an entity can effectively operate or function.
-
D.
orbitAltitude
Indicates the height of an object's orbit above a reference body, typically measured from the body's surface or mean radius.
-
E.
explosionAltitude
Indicates the height above a reference surface at which an explosion occurs or is triggered.
- 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_69a498f912008190a376a98b207b2071 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c2f314c081909c0ab80397d96abb |
completed | March 1, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69a4befb08b88190be966fa1aadd4bcd |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:57 p.m.