Triple
T20347837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | France at the Eurovision Song Contest 2009 |
E495918
|
entity |
| Predicate | finalPoints |
P2625
|
FINISHED |
| Object | 107 |
—
|
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: 107 | Statement: [France at the Eurovision Song Contest 2009, finalPoints, 107]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalPoints Context triple: [France at the Eurovision Song Contest 2009, finalPoints, 107]
-
A.
finalScore
chosen
Indicates the resulting or overall score achieved after all contributing actions, events, or evaluations are completed.
-
B.
finalLeague
Indicates the league or competition in which an entity ultimately ends up or is officially classified, typically after all stages or transitions are complete.
-
C.
finalTeam
Indicates that an entity is the ultimate or concluding team associated with another entity or process.
-
D.
finalScoreWinner
Indicates that the referenced entity is the winner as determined by the final score of a game, match, or competition.
-
E.
finalMatches
Indicates that two or more items correspond exactly in their final or completed form, satisfying all criteria for being considered the same at the end state.
- 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_69e0b4a3320881909495ae8bc30bc2dc |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67839e7b48190876ce7133a20c65b |
completed | April 20, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69e57636b4808190bc2855af48a3ccdc |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:24 a.m.