Triple
T26753487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emirates Old Trafford |
E674604
|
entity |
| Predicate | sponsorshipWith |
P78082
|
FINISHED |
| Object | Emirates airline |
—
|
NE NERFINISHED |
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: Emirates airline | Statement: [Emirates Old Trafford, sponsorshipWith, Emirates airline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sponsorshipWith Context triple: [Emirates Old Trafford, sponsorshipWith, Emirates airline]
-
A.
sponsorTo
chosen
Indicates that one entity provides support, funding, or endorsement to another entity, typically to enable or promote the latter’s activities or initiatives.
-
B.
sponsorshipRenamedFrom
Indicates that a sponsorship currently known by one name previously existed under a different, earlier name.
-
C.
sponsorEnd
Indicates the point in time or condition at which a sponsorship relationship or sponsorship-related action comes to an end.
-
D.
sponsorFrom
Indicates that one entity provides sponsorship or financial backing originating from a specified source entity.
-
E.
sponsorInHouse
Indicates that one entity formally supports, promotes, or funds another entity within the same organization, institution, or internal setting.
- 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_69eecda6e9dc81908452fab3ba17ed9b |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f61a17a7788190946f7e32d63cd43f |
completed | May 2, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69f611ab768c8190b1849c15a3e59dda |
completed | May 2, 2026, 3 p.m. |
Created at: April 27, 2026, 3:54 a.m.