Triple
T31916105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fairytale |
E814835
|
entity |
| Predicate | eurovisionFinalPlacement |
P164249
|
FINISHED |
| Object | 1st place |
—
|
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: 1st place | Statement: [Fairytale, eurovisionFinalPlacement, 1st place]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eurovisionFinalPlacement Context triple: [Fairytale, eurovisionFinalPlacement, 1st place]
-
A.
eurovisionFinalResult
Indicates the final placement or outcome achieved by an entry or participant in the Eurovision Song Contest.
-
B.
achievedPlaceAtEurovision
chosen
Indicates the final placement or ranking an entity obtained 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.
eurovisionRunningOrderPosition
Indicates the specific position in which an entry appears in the running order of a Eurovision Song Contest show.
-
E.
performedInEurovisionFinal
Indicates that an entity (typically a performer or act) took part in the final round of the Eurovision Song Contest.
- 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_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:02 a.m.