Triple
T2233404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunshine on Leith |
E49222
|
entity |
| Predicate | commonlySungAt |
P32287
|
FINISHED |
| Object | Hibernian F.C. home matches |
—
|
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: Hibernian F.C. home matches | Statement: [Sunshine on Leith, commonlySungAt, Hibernian F.C. home matches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonlySungAt Context triple: [Sunshine on Leith, commonlySungAt, Hibernian F.C. home matches]
-
A.
isTraditionallySungBy
chosen
Indicates that something, typically a song or chant, is customarily performed vocally by a particular person, group, or type of performer according to tradition.
-
B.
commonlySungStanzas
Indicates that certain stanzas of a song or poem are those most frequently sung or performed in practice.
-
C.
singsSong
Indicates that an entity performs the act of singing a particular song.
-
D.
sungAs
Indicates that something is performed or vocalized in the manner, role, or identity specified by another entity (e.g., a song or part being sung as a particular character, style, or version).
-
E.
performedSong
Indicates that an entity (such as an artist or performer) has given a performance of a particular song.
- 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_69a88aa84bdc819086df50e9c20b301e |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc0913f1c8190ac9cfeb0f1c84a76 |
completed | March 7, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_69abbdadbb0c8190b3a1ede31b8acbfa |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.