Triple
T2349109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNITED |
E47402
|
entity |
| Predicate | communicationPurpose |
P79
|
FINISHED |
| Object | aircraft identification in ATC communications |
—
|
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: aircraft identification in ATC communications | Statement: [UNITED, communicationPurpose, aircraft identification in ATC communications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communicationPurpose Context triple: [UNITED, communicationPurpose, aircraft identification in ATC communications]
-
A.
communicationPrinciple
Indicates a guiding rule or norm that shapes how communication should be conducted between entities.
-
B.
purpose
chosen
Indicates that one entity exists, is done, or is used in order to achieve, support, or serve the goal, function, or intended outcome of another entity.
-
C.
communicationChannel
Indicates a medium or method through which information is transmitted between parties.
-
D.
communicationMode
Indicates the method or channel through which communication between entities is carried out.
-
E.
communicationModel
Indicates the type or framework of communication used or assumed in the relationship between entities.
- 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_69a88a1b678c8190bce986922ba60ce0 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abcb802da08190980100444010f91e |
completed | March 7, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69abc5981ce48190a3f7852d28276e11 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:54 p.m.