Triple
T22514956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Widerøe |
E556616
|
entity |
| Predicate | callsignUsage |
P1565
|
FINISHED |
| Object | used in air traffic control 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: used in air traffic control communications | Statement: [Widerøe, callsignUsage, used in air traffic control communications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: callsignUsage Context triple: [Widerøe, callsignUsage, used in air traffic control communications]
-
A.
relatedCallsignUsage
Indicates that one callsign is used in connection with, or as a variant of, another callsign in operational or identification contexts.
-
B.
callsign
chosen
Indicates that an entity is assigned or uses a specific radio or identification callsign as its designated identifier in communication contexts.
-
C.
callsignCondition
Indicates a condition or constraint that must be satisfied by an entity’s callsign within the relationship or context.
-
D.
callsignOfOperator
Indicates that one entity is the radio or communication callsign assigned to or used by another entity acting as an operator.
-
E.
callsignLanguage
Indicates the language in which a callsign is expressed or encoded.
- 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_69e11e555edc81909ca803587dafd747 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15e2c3098819098a553133cc9515b |
completed | April 29, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69ee625e3b408190a60c759fb0b28fe2 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:50 p.m.