Triple
T10467975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eurovision Song Contest 1991 |
E246849
|
entity |
| Predicate | pointsForWinner |
P7114
|
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, pointsForWinner, 146]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pointsForWinner Context triple: [Eurovision Song Contest 1991, pointsForWinner, 146]
-
A.
pointsForWin
Indicates the number of points awarded to an entity for achieving a win in a given context or competition.
-
B.
winnerPoints
chosen
Indicates the number of points earned by the winning participant or entity in a competition or event.
-
C.
finalScoreWinner
Indicates that the referenced entity is the winner as determined by the final score of a game, match, or competition.
-
D.
positionOfWinner
Indicates the relationship that identifies which entity holds the winning position or rank in a competition or contest.
-
E.
winnerCount
Indicates the number of entities that are designated as winners in a given context or event.
- 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.