Triple
T28488416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eurovision Song Contest 1968 |
E720895
|
entity |
| Predicate | finalScoreOfUnitedKingdom |
P2625
|
FINISHED |
| Object | 28 |
—
|
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: 28 | Statement: [Eurovision Song Contest 1968, finalScoreOfUnitedKingdom, 28]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalScoreOfUnitedKingdom Context triple: [Eurovision Song Contest 1968, finalScoreOfUnitedKingdom, 28]
-
A.
outcomeForUnitedKingdom
Indicates the result, consequence, or impact that something has specifically for the United Kingdom.
-
B.
resultForGreatBritain
Indicates the outcome or performance achieved specifically by Great Britain in a given event, context, or measurement.
-
C.
outcomeForEngland
Indicates the result or consequence that an event, action, or situation has specifically for England.
-
D.
finalScore
chosen
Indicates the resulting or overall score achieved after all contributing actions, events, or evaluations are completed.
-
E.
numberOfEnglandGoals
Indicates the number of goals scored by the England team in a given match or context.
- 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_69f01a5a47148190b0a7e111bc432e0a |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: April 28, 2026, 3 a.m.