Triple
T10550637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Class G airspace |
E248937
|
entity |
| Predicate | pilotResponsibility |
P61259
|
FINISHED |
| Object | see and avoid other 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: see and avoid other aircraft | Statement: [Class G airspace, pilotResponsibility, see and avoid other aircraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pilotResponsibility Context triple: [Class G airspace, pilotResponsibility, see and avoid other aircraft]
-
A.
pilotRequirement
Indicates that a certain condition, qualification, or resource is required in order for a pilot to operate or perform a specified activity.
-
B.
isNotedByPilotsAs
Indicates that something is recognized, remarked upon, or specifically mentioned by pilots.
-
C.
airspaceRole
chosen
Indicates the specific function or responsibility an entity has within a defined airspace.
-
D.
typicalPilotPosition
Indicates the usual or standard spatial position or placement where a pilot is located relative to the associated object or system.
-
E.
usedByPilotsOf
Indicates that something is utilized or operated by pilots belonging to a particular aircraft, organization, or group.
- 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_69d381c733c08190ab1dd6239f5f34ae |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d52710869c81909b6db1a190825bad |
completed | April 7, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69d518fa0b4081909bffc936d78bd77b |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:34 p.m.