Triple
T20347862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | France at the Eurovision Song Contest 2009 |
E495918
|
entity |
| Predicate | resultInTelevote |
P55852
|
FINISHED |
| Object | lower than jury result |
—
|
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: lower than jury result | Statement: [France at the Eurovision Song Contest 2009, resultInTelevote, lower than jury result]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultInTelevote Context triple: [France at the Eurovision Song Contest 2009, resultInTelevote, lower than jury result]
-
A.
voteResult
Indicates the outcome or decision produced by a voting process involving the related entities.
-
B.
eurovisionFinalResult
Indicates the final placement or outcome achieved by an entry or participant in the Eurovision Song Contest.
-
C.
eurovisionPoints
Indicates the number of points one participant or country awards to another in the Eurovision Song Contest.
-
D.
voteCount
Indicates the number of votes that have been cast for or associated with a particular item or option.
-
E.
popularVoteOutcome
chosen
Indicates the result of a popular vote, specifying which option or candidate received the majority or winning share of votes.
- 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.