Triple
T23792585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Listen to Your Heartbeat |
E588442
|
entity |
| Predicate | musicCompetition |
P54102
|
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: [Listen to Your Heartbeat, musicCompetition, Eurovision Song Contest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicCompetition Context triple: [Listen to Your Heartbeat, musicCompetition, Eurovision Song Contest]
-
A.
programCompetition
Indicates a competitive relationship between programs, where programs are compared or ranked against each other in some contest or evaluation.
-
B.
musicContestsIncluded
chosen
Indicates that certain music contests are part of, or included within, a larger event, program, or collection.
-
C.
competitionHeld
Indicates that a competitive event takes place or is organized at a particular time and/or location.
-
D.
countryCompetition
Indicates a competitive relationship or rivalry that exists between countries, such as in economics, politics, or international events.
-
E.
competitionEnd
Indicates that a competitive event or contest has concluded or reached its final state.
- 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_69e25d15db58819092ac1e6791696fd9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c6d939c08190997246abe5781b83 |
completed | April 29, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:36 p.m.