Triple
T24812082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SA-3 Goa |
E620816
|
entity |
| Predicate | operationalAltitudeBand |
P60638
|
FINISHED |
| Object | low 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: low altitude | Statement: [SA-3 Goa, operationalAltitudeBand, low altitude]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationalAltitudeBand Context triple: [SA-3 Goa, operationalAltitudeBand, low altitude]
-
A.
operationalAltitude
chosen
Indicates the typical or designated altitude at which an entity is intended to operate.
-
B.
flightLevelRange
Indicates the range of permissible or actual flight levels associated with an aircraft’s operation or a specific flight segment.
-
C.
appliesToAirspaceOf
Indicates that a rule, restriction, or condition is specifically relevant to, or in effect within, a particular airspace.
-
D.
airspaceType
Indicates the classification or category of airspace that applies to a given location or flight segment.
-
E.
extendsToApproximateAltitude
Indicates that something reaches or stretches up to a specified altitude value, which is understood to be approximate rather than exact.
- 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_69e2fabfd4648190bd0e5c7f4dbb6cab |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
Created at: April 18, 2026, 4:50 a.m.