Triple
T10517930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SCANDINAVIAN |
E248082
|
entity |
| Predicate | usedInAviationCommunication |
P94343
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [SCANDINAVIAN, usedInAviationCommunication, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInAviationCommunication Context triple: [SCANDINAVIAN, usedInAviationCommunication, yes]
-
A.
usedInAviation
Indicates that something is employed or applied within the field or context of aviation.
-
B.
usedInAirTrafficControlFor
Indicates that something serves as a tool, system, or resource specifically employed in the management, monitoring, or regulation of air traffic.
-
C.
usedInAviationNavigation
Indicates that something is employed as a tool, method, or system for aiding navigation in aviation contexts.
-
D.
usedInAviationCodeContext
Indicates that something is employed or referenced within the context of aviation-related codes or coding systems.
-
E.
usedInAviationAs
Indicates that something serves a particular role, function, or application within the field of aviation.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509cd0fb8819087de2f9a93bad6e6 |
completed | April 7, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69d4fb94fa10819091f585bab4379c6f |
completed | April 7, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69d4fe06d4a48190b1a45dd1d4e16df0 |
completed | April 7, 2026, 12:52 p.m. |
Created at: April 6, 2026, 12:28 p.m.