Triple
T10886491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Class E airspace |
E257059
|
entity |
| Predicate | providesATCServiceTo |
P96239
|
FINISHED |
| Object | IFR aircraft |
—
|
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: IFR aircraft | Statement: [Class E airspace, providesATCServiceTo, IFR aircraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesATCServiceTo Context triple: [Class E airspace, providesATCServiceTo, IFR aircraft]
-
A.
airTraffic
Indicates the movement and flow of aircraft through airspace, including their routes, density, and interactions while in flight.
-
B.
appliesToAirspaceOf
Indicates that a rule, restriction, or condition is specifically relevant to, or in effect within, a particular airspace.
-
C.
aircraftFacility
Indicates that a facility is designed, equipped, or used to support the operation, maintenance, or accommodation of aircraft.
-
D.
flightRules
Indicates the regulatory or procedural rules that govern how a flight must be conducted or operated.
-
E.
operationalControlOfFlights
Indicates that one entity has the authority and responsibility to manage and direct the operation of specific flights conducted by another entity.
- 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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d751dea1a88190b916879be8d74413 |
completed | April 9, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69d70d3943c881908895397eccc3e415 |
completed | April 9, 2026, 2:21 a.m. |
| PDg | Predicate description generation | batch_69d7101de31c819090707635f6790559 |
completed | April 9, 2026, 2:34 a.m. |
Created at: April 8, 2026, 9:21 p.m.