Triple
T34019682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eurovision Song Contest 1976 |
E872347
|
entity |
| Predicate | winningCountryPointsMargin |
P39190
|
FINISHED |
| Object | 17 |
—
|
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: 17 | Statement: [Eurovision Song Contest 1976, winningCountryPointsMargin, 17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: winningCountryPointsMargin Context triple: [Eurovision Song Contest 1976, winningCountryPointsMargin, 17]
-
A.
finalRoundMargin
chosen
Indicates the point or score difference between competitors in the final round of a contest or competition.
-
B.
defeatedByMargin
Indicates that one entity was defeated by another with a specified numerical margin or difference in score, votes, or performance.
-
C.
averageMarginOfVictory
Indicates the typical point or score difference by which one competitor or team wins over opponents across a set of contests or games.
-
D.
marginOfVictoryPercentage
Indicates the percentage difference between the winner’s and the runner-up’s scores or votes in a contest or competition.
-
E.
scoreMargin
Indicates the difference in score between two competitors or sides in a contest or game.
- 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_69f349a19ad88190ab586f010c804a8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:51 a.m.