Triple
T30296514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DOKOM |
E770533
|
entity |
| Predicate | usedByAirTrafficControllers |
P84588
|
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: [DOKOM, usedByAirTrafficControllers, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByAirTrafficControllers Context triple: [DOKOM, usedByAirTrafficControllers, yes]
-
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.
cooperatedWithATC
Indicates that an entity worked collaboratively and in coordination with air traffic control (ATC) during a flight or aviation-related operation.
-
D.
airTrafficRole
Indicates the specific function or responsibility an entity has within the context of air traffic operations or control.
-
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_69f224881b948190b8c4921b250a44a3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: April 29, 2026, 7:48 p.m.