Triple
T11157946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ARE |
E263958
|
entity |
| Predicate | airlineGroupScope |
P98144
|
FINISHED |
| Object | multinational airline group |
—
|
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: multinational airline group | Statement: [ARE, airlineGroupScope, multinational airline group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airlineGroupScope Context triple: [ARE, airlineGroupScope, multinational airline group]
-
A.
airlineAllianceScope
Indicates the extent or coverage of an airline alliance’s operations or cooperation (e.g., regional vs. global).
-
B.
associatedAirlineGroup
Indicates a relationship where an airline is linked or belongs to a specific airline group or alliance.
-
C.
airlineAllianceRole
Indicates the specific role or function an airline holds within an airline alliance.
-
D.
airlineAllianceContext
Indicates the contextual relationship between an airline and its membership or participation status within a specific airline alliance.
-
E.
airlineAllianceMembership
Indicates that an airline is a member of a specific airline alliance.
- 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_69d6aa9ccddc8190868998c8b7beb060 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e87fe9a881909540ecc4ed9b6b9f |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75cec26fc8190a5497d186306f935 |
completed | April 9, 2026, 8:01 a.m. |
| PDg | Predicate description generation | batch_69d7706116248190a87440bec3960884 |
completed | April 9, 2026, 9:24 a.m. |
Created at: April 8, 2026, 9:28 p.m.