Triple
T10467973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eurovision Song Contest 1991 |
E246849
|
entity |
| Predicate | tieForFirstPlace |
P94193
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Eurovision Song Contest 1991, tieForFirstPlace, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tieForFirstPlace Context triple: [Eurovision Song Contest 1991, tieForFirstPlace, true]
-
A.
tiebreaker
Indicates that one entity serves as the deciding factor used to break a tie between two or more otherwise equal options or outcomes.
-
B.
firstWinner
Indicates that the subject is the entity who achieved first place or victory in the referenced event or competition.
-
C.
givesFirstPickTo
Indicates that one entity grants another entity the right to choose first among available options.
-
D.
winnerTakeAll
Indicates that one participant receives all the benefits, rewards, or outcomes from a competition or situation, leaving none for the others.
-
E.
firstToAchieve
Indicates that one entity was the earliest or initial entity to accomplish or attain a specified goal, status, or outcome before any others.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69d4fe058fcc81909428137d9ffd6d90 |
completed | April 7, 2026, 12:52 p.m. |
Created at: April 6, 2026, 12:20 p.m.