Triple
T37026457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA Cup trophy |
E916368
|
entity |
| Predicate | usedAsOfficialTrophyUntil |
P143094
|
FINISHED |
| Object | 2008–09 season |
—
|
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: 2008–09 season | Statement: [UEFA Cup trophy, usedAsOfficialTrophyUntil, 2008–09 season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsOfficialTrophyUntil Context triple: [UEFA Cup trophy, usedAsOfficialTrophyUntil, 2008–09 season]
-
A.
isFormerChampionshipTrophyOf
chosen
Indicates that an object previously served as the official championship trophy awarded for a particular competition or title.
-
B.
trophyOfficialName
Indicates the official, formally recognized name assigned to a particular trophy.
-
C.
isPlayoffTrophyOf
Indicates that a trophy is awarded to and associated with a particular team or competition as the result of a playoff victory.
-
D.
namedAfterTrophy
Indicates that one entity has been given a name derived from or in honor of a particular trophy.
-
E.
commemorativeTrophy
Indicates that a trophy exists to honor or memorialize a particular person, event, or achievement.
- 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_69f76e92c7648190bcfa277f64c71a21 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fef2db323c8190821bda53f22a42be |
completed | May 9, 2026, 8:39 a.m. |
| PD | Predicate disambiguation | batch_69fef21d63c88190abf6a99b59b3c655 |
completed | May 9, 2026, 8:36 a.m. |
Created at: May 3, 2026, 4:14 p.m.