Triple
T10739342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SWISS |
E253279
|
entity |
| Predicate | usedInRadioCommunication |
P94343
|
FINISHED |
| Object | air traffic control |
—
|
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: air traffic control | Statement: [SWISS, usedInRadioCommunication, air traffic control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInRadioCommunication Context triple: [SWISS, usedInRadioCommunication, air traffic control]
-
A.
usedInTelecommunications
Indicates that something is employed as a component, tool, or method within telecommunications systems or processes.
-
B.
usedInAviationCommunication
chosen
Indicates that something (such as a term, signal, or technology) is employed within the context of aviation-related communication.
-
C.
usedInRadioBroadcasts
Indicates that something is employed or featured as part of radio broadcasts.
-
D.
usedToCommunicate
Indicates that one entity serves as a medium or tool through which another entity conveys information, messages, or signals.
-
E.
usedInDigitalCommunication
Indicates that something is employed as a medium, tool, or element within digital or electronic communication processes.
- 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d710424d8c81908ee9b59d622f2af5 |
completed | April 9, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69d6f30df9948190ab3cdc33977fac14 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:14 p.m.