Triple
T35862788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PAHN |
E1036998
|
entity |
| Predicate | usesForAirTrafficControl |
P84588
|
FINISHED |
| Object | Haines Airport |
—
|
NE NERFINISHED |
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: Haines Airport | Statement: [PAHN, usesForAirTrafficControl, Haines Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesForAirTrafficControl Context triple: [PAHN, usesForAirTrafficControl, Haines Airport]
-
A.
usedInAirTrafficControlFor
chosen
Indicates that something serves as a tool, system, or resource specifically employed in the management, monitoring, or regulation of air traffic.
-
B.
usedInAviationCommunication
Indicates that something (such as a term, signal, or technology) is employed within the context of aviation-related communication.
-
C.
usedByAircraftRegisteredIn
Indicates that something (such as equipment, a system, or a facility) is utilized by aircraft that are registered in a specified jurisdiction or registry.
-
D.
appliesToAirspaceOf
Indicates that a rule, restriction, or condition is specifically relevant to, or in effect within, a particular airspace.
-
E.
usedInAviation
Indicates that something is employed or applied within the field or context of aviation.
- 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_69f76e1d279c8190843e5b64a0a12c3f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b2c771108190adeec151daad5dab |
completed | May 3, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:06 p.m.