Triple
T28537816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2U |
E722212
|
entity |
| Predicate | airlineAffiliationType |
P97733
|
FINISHED |
| Object | brand operated in conjunction with El Al |
—
|
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: brand operated in conjunction with El Al | Statement: [2U, airlineAffiliationType, brand operated in conjunction with El Al]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airlineAffiliationType Context triple: [2U, airlineAffiliationType, brand operated in conjunction with El Al]
-
A.
airlineAllianceMembership
Indicates that an airline is a member of a specific airline alliance.
-
B.
airlineAllianceType
Indicates the specific airline alliance or partnership group to which an airline or flight operation belongs.
-
C.
airlineAssociation
chosen
Indicates a formal relationship or affiliation between an airline and another entity, such as a partner, alliance, or associated organization.
-
D.
airlineAllianceRelationship
Indicates that two or more airlines are connected through a formal alliance or partnership arrangement.
-
E.
airlineAllianceStatus
Indicates the formal alliance membership or partnership status that exists between an airline and an airline alliance.
- 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_69f01a5e42348190b1ffbca26e739c84 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 3:33 a.m.