Triple
T33575904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waterloo |
E860027
|
entity |
| Predicate | votedBestEurovisionSong |
P68398
|
FINISHED |
| Object | 2005 EBU anniversary show |
—
|
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: 2005 EBU anniversary show | Statement: [Waterloo, votedBestEurovisionSong, 2005 EBU anniversary show]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: votedBestEurovisionSong Context triple: [Waterloo, votedBestEurovisionSong, 2005 EBU anniversary show]
-
A.
EurovisionWinningSongForCountry
Indicates that a particular song is the one that won the Eurovision Song Contest for a given country in a specific year.
-
B.
yearOfEurovisionVictory
Indicates the specific year in which an entity achieved victory in the Eurovision Song Contest.
-
C.
eurovisionFinalResult
Indicates the final placement or outcome achieved by an entry or participant in the Eurovision Song Contest.
-
D.
performanceLanguageAtEurovision
Indicates the language in which a musical performance is delivered at the Eurovision Song Contest.
-
E.
significanceForEurovision
chosen
Indicates the degree to which something is important, influential, or relevant in the context of the Eurovision Song Contest.
- 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_69f3497d37848190afcbb5ef3f5c7376 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f74c503c8190b462600d76696b2f |
completed | May 3, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:40 a.m.