Triple
T33879627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Area Control Center |
E868448
|
entity |
| Predicate | responsibleForPhaseOfFlight |
P21768
|
FINISHED |
| Object | en-route phase |
—
|
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: en-route phase | Statement: [Area Control Center, responsibleForPhaseOfFlight, en-route phase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: responsibleForPhaseOfFlight Context triple: [Area Control Center, responsibleForPhaseOfFlight, en-route phase]
-
A.
controlsPhaseOfFlight
chosen
Indicates that one entity has authority over or manages a specific phase of another entity’s flight operation.
-
B.
flightPhase
Indicates the specific stage or phase of an aircraft’s operation within a flight (e.g., taxi, takeoff, climb, cruise, descent, landing).
-
C.
aircraftRoleDuringFlight
Indicates the specific function or role an aircraft fulfills while it is in flight.
-
D.
testFlightPhase
Indicates the specific phase or stage of a test flight that an aircraft or system is currently in.
-
E.
phaseOfFlightAtBirdStrike
Indicates the specific phase of an aircraft’s flight during which a bird strike occurred.
- 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_69f34995b81c8190acdb45cea5a10eff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:48 a.m.