Triple
T33771967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fångad av en stormvind |
E865405
|
entity |
| Predicate | belongsToContest |
P199293
|
FINISHED |
| Object | Eurovision Song Contest |
—
|
NE NERFINISHED |
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: Eurovision Song Contest | Statement: [Fångad av en stormvind, belongsToContest, Eurovision Song Contest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToContest Context triple: [Fångad av en stormvind, belongsToContest, Eurovision Song Contest]
-
A.
losesContestTo
Indicates that one participant is defeated by another in a contest or competition.
-
B.
tieneCompetenciaEn
Indicates that an entity possesses skill, expertise, or competence in a specific area, field, or activity.
-
C.
betrothedByContest
Indicates that an entity becomes engaged or promised in marriage to another as the result of winning or being awarded through a contest or competition.
-
D.
alsoContestedIn
Indicates that the same issue, claim, or matter is being disputed or challenged in another context, case, or proceeding as well.
-
E.
trophyContestedBy
Indicates that a particular trophy is the object of competition among the specified participants or teams.
- 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_69f3498df6f88190bf9647ea4e4a956e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff2d22ffb48190ae58ddf3c7e02869 |
completed | May 9, 2026, 12:48 p.m. |
| PD | Predicate disambiguation | batch_69ff2ac2e1c4819096cc64e94aef2ff0 |
completed | May 9, 2026, 12:38 p.m. |
| PDg | Predicate description generation | batch_69ff2d21f0a48190ad2ef5901cb07d93 |
completed | May 9, 2026, 12:48 p.m. |
Created at: May 1, 2026, 1:45 a.m.