Triple
T23151614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SU30 |
E578336
|
entity |
| Predicate | flightRulesUsage |
P8780
|
FINISHED |
| Object | IFR |
—
|
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 | Statement: [SU30, flightRulesUsage, IFR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flightRulesUsage Context triple: [SU30, flightRulesUsage, IFR]
-
A.
flightRules
chosen
Indicates the regulatory or procedural rules that govern how a flight must be conducted or operated.
-
B.
airTraffic
Indicates the movement and flow of aircraft through airspace, including their routes, density, and interactions while in flight.
-
C.
runwayUsage
Indicates that a particular runway is being used or assigned for aircraft operations such as takeoffs or landings.
-
D.
supportsInstrumentFlightRulesOperations
Indicates that an entity enables or accommodates operations conducted under Instrument Flight Rules (IFR).
-
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.
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_69e245fb8de081908f0eba7b5fd75bc4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18ef982488190984a6358bdcd577c |
completed | April 29, 2026, 4:54 a.m. |
| PD | Predicate disambiguation | batch_69ef89f83b108190aaaa1db6221fc163 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:01 p.m.