Triple
T5765301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CUBANA |
E127198
|
entity |
| Predicate | radioCommunicationRole |
P1565
|
FINISHED |
| Object | air traffic control identification |
—
|
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 identification | Statement: [CUBANA, radioCommunicationRole, air traffic control identification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radioCommunicationRole Context triple: [CUBANA, radioCommunicationRole, air traffic control identification]
-
A.
radioInterface
Indicates a relationship where one entity provides or defines the radio communication interface used by another entity for wireless connectivity or control.
-
B.
communicationModelRole
Indicates the role an entity plays within a communication model, specifying its function or position in the communication process.
-
C.
broadcastRole
Indicates that an entity has a specific role or function within a broadcast or transmission context.
-
D.
radioAnnouncers
Indicates that one entity serves as a radio announcer for, or in association with, another entity.
-
E.
callsign
chosen
Indicates that an entity is assigned or uses a specific radio or identification callsign as its designated identifier in communication contexts.
- 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_69c00834f6308190851b0abeddd8ed7e |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02acb12c081908e4beee4a957f9f9 |
completed | March 22, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69c021ce8d3c81909b332cb1c33a61ad |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:49 p.m.