Triple
T9738095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Wings Airlines |
E236115
|
entity |
| Predicate | callsignUsedFor |
P1565
|
FINISHED |
| Object | air-ground radio communication |
—
|
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-ground radio communication | Statement: [Red Wings Airlines, callsignUsedFor, air-ground radio communication]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: callsignUsedFor Context triple: [Red Wings Airlines, callsignUsedFor, air-ground radio communication]
-
A.
callsign
chosen
Indicates that an entity is assigned or uses a specific radio or identification callsign as its designated identifier in communication contexts.
-
B.
callsignOfOperator
Indicates that one entity is the radio or communication callsign assigned to or used by another entity acting as an operator.
-
C.
callsignCondition
Indicates a condition or constraint that must be satisfied by an entity’s callsign within the relationship or context.
-
D.
relatedCallsignUsage
Indicates that one callsign is used in connection with, or as a variant of, another callsign in operational or identification contexts.
-
E.
callsignSeries
Indicates that one entity is a member or installment within a series or sequence that shares the same callsign.
- 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_69ca84d313e88190983ee6ffd0ef60d2 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9ef2ba048190811d6f4251fdb270 |
completed | April 1, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69cd03c6ffc88190a5e9569e19122ad5 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:22 p.m.