Triple
T10739330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LX |
E253278
|
entity |
| Predicate | airlineAllianceMembershipSince |
P40149
|
FINISHED |
| Object | 2006 |
—
|
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: 2006 | Statement: [LX, airlineAllianceMembershipSince, 2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airlineAllianceMembershipSince Context triple: [LX, airlineAllianceMembershipSince, 2006]
-
A.
airlineAllianceJoinDate
chosen
Indicates the date on which an airline became a member of a particular airline alliance.
-
B.
airlineAllianceMembership
Indicates that an airline is a member of a specific airline alliance.
-
C.
airlineAllianceStatus
Indicates the formal alliance membership or partnership status that exists between an airline and an airline alliance.
-
D.
airlineAllianceType
Indicates the specific airline alliance or partnership group to which an airline or flight operation belongs.
-
E.
airlineAllianceRelationship
Indicates that two or more airlines are connected through a formal alliance or partnership arrangement.
- 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d710424d8c81908ee9b59d622f2af5 |
completed | April 9, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69d6f30df9948190ab3cdc33977fac14 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:14 p.m.