Triple
T33576018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waterloo |
E860029
|
entity |
| Predicate | eurovisionVotingSystem |
P177431
|
FINISHED |
| Object | 10-point jury system |
—
|
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: 10-point jury system | Statement: [Waterloo, eurovisionVotingSystem, 10-point jury system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eurovisionVotingSystem Context triple: [Waterloo, eurovisionVotingSystem, 10-point jury system]
-
A.
eurovisionPoints
Indicates the number of points one participant or country awards to another in the Eurovision Song Contest.
-
B.
eurovisionFinalResult
Indicates the final placement or outcome achieved by an entry or participant in the Eurovision Song Contest.
-
C.
eurovisionSemiFinalPoints
Indicates the number of points one participant awards to another in a Eurovision Song Contest semi-final.
-
D.
eurovisionRunningOrderPosition
Indicates the specific position in which an entry appears in the running order of a Eurovision Song Contest show.
-
E.
significanceForEurovision
Indicates the degree to which something is important, influential, or relevant in the context of the Eurovision Song Contest.
- F. None of above. chosen
Provenance (4 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_69f6fb93224881908fc66fe76115fcdb |
completed | May 3, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f6fb17d5ec81909091e37e1ddbe577 |
completed | May 3, 2026, 7:36 a.m. |
Created at: May 1, 2026, 1:40 a.m.