Triple
T33575726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eurovision Song Contest 1975 |
E860023
|
entity |
| Predicate | scoringMaximumPerJury |
P156337
|
FINISHED |
| Object | 58 points |
—
|
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: 58 points | Statement: [Eurovision Song Contest 1975, scoringMaximumPerJury, 58 points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scoringMaximumPerJury Context triple: [Eurovision Song Contest 1975, scoringMaximumPerJury, 58 points]
-
A.
pointsPerJury
chosen
Indicates the number of points assigned or awarded by each individual jury in an evaluation or scoring process.
-
B.
hasJudgesScore
Indicates that a judging entity assigns or is associated with a specific score or rating for another entity or performance.
-
C.
numberOfJudges
Indicates the total count of judges associated with a particular case, event, or entity.
-
D.
judgesAre
Indicates that one entity serves as a judge or evaluator of another entity.
-
E.
judgesMayBe
Indicates that certain individuals can serve in the role of judges under specified conditions or classifications.
- 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_69f6f74b95248190a3546b33dda2402d |
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.