Triple
T24241647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eurovision Song Contest 1966 |
E603242
|
entity |
| Predicate | winnerPerformer |
P46350
|
FINISHED |
| Object | Udo Jürgens |
—
|
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: Udo Jürgens | Statement: [Eurovision Song Contest 1966, winnerPerformer, Udo Jürgens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: winnerPerformer Context triple: [Eurovision Song Contest 1966, winnerPerformer, Udo Jürgens]
-
A.
winningPerformer
chosen
Indicates that the referenced performer is the one who achieved victory or first place in a particular competition, event, or contest.
-
B.
winnerManager
Indicates that one entity is the manager or supervisor of another entity who is the winner in a given context or competition.
-
C.
winnerDam
Indicates that the subject entity is the dam (mother) of an offspring that has won a specified race or competition.
-
D.
winnerType
Indicates the category or kind of winner associated with an event, competition, or outcome.
-
E.
winnerMake
Indicates that one entity causes or brings about another entity becoming the winner in a contest, competition, or selection process.
- 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_69e2953f631c819097cbb421046bd417 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28aa04fe08190922d6abde695571a |
completed | April 29, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:03 a.m.