Triple
T22365932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CYYC |
E552903
|
entity |
| Predicate | usedInAviationCharts |
P147379
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [CYYC, usedInAviationCharts, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInAviationCharts Context triple: [CYYC, usedInAviationCharts, yes]
-
A.
usedInAviationNavigation
Indicates that something is employed as a tool, method, or system for aiding navigation in aviation contexts.
-
B.
usedInAviation
Indicates that something is employed or applied within the field or context of aviation.
-
C.
usedInFlightPlansFor
Indicates that something (e.g., data, a procedure, or a resource) is employed as part of creating or executing flight plans for specific flights or routes.
-
D.
usedInAviationCommunication
Indicates that something (such as a term, signal, or technology) is employed within the context of aviation-related communication.
-
E.
usedInAirTrafficControlFor
Indicates that something serves as a tool, system, or resource specifically employed in the management, monitoring, or regulation of air traffic.
- 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_69e11e4affcc8190ba7c27d29062558d |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1580074dc819091305ac7017000d3 |
completed | April 29, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69e73011e6388190a05edf137f488441 |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e7342e9a0081909257210a81c96b29 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:44 p.m.