Triple
T10517594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terminal Radar Approach Control |
E248073
|
entity |
| Predicate | controlsAirspaceAround |
P22328
|
FINISHED |
| Object | major airports |
—
|
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: major airports | Statement: [Terminal Radar Approach Control, controlsAirspaceAround, major airports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlsAirspaceAround Context triple: [Terminal Radar Approach Control, controlsAirspaceAround, major airports]
-
A.
appliesToAirspaceOf
Indicates that a rule, restriction, or condition is specifically relevant to, or in effect within, a particular airspace.
-
B.
rangeAgainstAircraft
Indicates that one entity measures, determines, or engages the distance to an aircraft target.
-
C.
hasAirspace
chosen
Indicates that one entity possesses, controls, or is associated with a defined region of airspace relative to another entity or area.
-
D.
airspaceType
Indicates the classification or category of airspace that applies to a given location or flight segment.
-
E.
airspaceRole
Indicates the specific function or responsibility an entity has within a defined airspace.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509cd0fb8819087de2f9a93bad6e6 |
completed | April 7, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69d4fb94fa10819091f585bab4379c6f |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:28 p.m.