Triple
T6797401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NOR SHUTTLE |
E156091
|
entity |
| Predicate | radioServiceType |
P73041
|
FINISHED |
| Object | aircraft radio callsign |
—
|
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 radio callsign | Statement: [NOR SHUTTLE, radioServiceType, aircraft radio callsign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radioServiceType Context triple: [NOR SHUTTLE, radioServiceType, aircraft radio callsign]
-
A.
radioTelephonyDesignatorFor
Indicates that one entity is the assigned radiotelephony (spoken) call sign or designator used in radio communications for another entity.
-
B.
radioFormat
Indicates the specific type or style of radio programming or broadcast format associated with an entity.
-
C.
radioInterface
Indicates a relationship where one entity provides or defines the radio communication interface used by another entity for wireless connectivity or control.
-
D.
radioAnnouncers
Indicates that one entity serves as a radio announcer for, or in association with, another entity.
-
E.
radioExperimentType
Indicates the specific kind or category of radio-related experiment being conducted or referenced.
- F. None of above. chosen
Provenance (4 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_69c6881844448190a65822d9b39d7f88 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2ca0c288190a990180fb7cfd08f |
completed | March 27, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69c6d099bf08819089a9f9894d037e74 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d2a8f9188190abbb8c730e7b5edf |
completed | March 27, 2026, 6:55 p.m. |
Created at: March 27, 2026, 2:15 p.m.