Triple
T15777469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eurovision Song Contest 2012 |
E382525
|
entity |
| Predicate | pointsOfWinner |
P7114
|
FINISHED |
| Object | 372 |
—
|
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: 372 | Statement: [Eurovision Song Contest 2012, pointsOfWinner, 372]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pointsOfWinner Context triple: [Eurovision Song Contest 2012, pointsOfWinner, 372]
-
A.
pointsForWin
Indicates the number of points awarded to an entity for achieving a win in a given context or competition.
-
B.
positionOfWinner
Indicates the relationship that identifies which entity holds the winning position or rank in a competition or contest.
-
C.
winnerPoints
chosen
Indicates the number of points earned by the winning participant or entity in a competition or event.
-
D.
pointsToWinSet
Indicates the number of points a player or side must win to secure the current set.
-
E.
pointsLeader
Indicates that the subject entity is the current leader in points relative to other entities in a given context or competition.
- 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_69d86da09a10819082fe9797b23e4664 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e05199cd8881909462462cec34d35a |
completed | April 16, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69e00531e7ac8190a4190cce4f7fab4c |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:47 a.m.