Triple
T25983444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Airways |
E646130
|
entity |
| Predicate | hasRoleInICAOContext |
P122515
|
FINISHED |
| Object | commercial air transport operator |
—
|
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: commercial air transport operator | Statement: [British Airways, hasRoleInICAOContext, commercial air transport operator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoleInICAOContext Context triple: [British Airways, hasRoleInICAOContext, commercial air transport operator]
-
A.
hasRoleInAviation
chosen
Indicates that an entity holds or has held a specific role, position, or function within the field of aviation.
-
B.
roleInCFMInternational
Indicates that an entity holds a specific role or position within the organization CFM International.
-
C.
hasRole
Indicates that an entity occupies, performs, or is assigned a specific role or function in relation to another entity or context.
-
D.
airspaceRole
Indicates the specific function or responsibility an entity has within a defined airspace.
-
E.
appliesToAirspaceOf
Indicates that a rule, restriction, or condition is specifically relevant to, or in effect within, a particular airspace.
- 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_69e77e881fc08190ba1c8dc7e2a07f97 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 22, 2026, 8:54 a.m.