Triple
T10467976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eurovision Song Contest 1991 |
E246849
|
entity |
| Predicate | pointsForSecondPlace |
P38172
|
FINISHED |
| Object | 146 |
—
|
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: 146 | Statement: [Eurovision Song Contest 1991, pointsForSecondPlace, 146]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pointsForSecondPlace Context triple: [Eurovision Song Contest 1991, pointsForSecondPlace, 146]
-
A.
secondPlace
Indicates that an entity holds the position of runner-up or finishes in second place in a ranked ordering, competition, or comparison relative to others.
-
B.
runnersUpPoints
Indicates the number of points awarded to an entity for finishing as a runner-up in a competition or ranking.
-
C.
secondRunnerUp
Indicates that one entity finished in third place in a competition or ranking relative to the others.
-
D.
runnerUpScore
chosen
Indicates the score achieved by the participant or entity that finished in second place in a competition or ranking.
-
E.
secondPlaceTime
Indicates the time at which an entity achieved second place in a ranked event or competition.
- 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_69d381c16c248190a2fe5b471e584e9c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5092ef810819093a4d1df83aeac09 |
completed | April 7, 2026, 1:39 p.m. |
| PD | Predicate disambiguation | batch_69d4fb84bafc8190819757b93620508a |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:20 p.m.