Triple
T25476822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | See the Bombers Fly Up |
E638455
|
entity |
| Predicate | isClubSongOf |
P158582
|
FINISHED |
| Object | Essendon Football Club |
—
|
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: Essendon Football Club | Statement: [See the Bombers Fly Up, isClubSongOf, Essendon Football Club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isClubSongOf Context triple: [See the Bombers Fly Up, isClubSongOf, Essendon Football Club]
-
A.
isSongIn
Indicates that a particular song is contained within or belongs to a specified collection, such as an album, playlist, or soundtrack.
-
B.
isForSong
Indicates that something is intended to be used with, associated with, or applicable to a particular song.
-
C.
isSignatureSongOf
Indicates that a particular song is widely recognized as the most iconic or defining song associated with a specific artist or group.
-
D.
isSongByBand
Indicates that a particular song is performed or created by a specific band.
-
E.
isPopularSongFor
Indicates that a song is widely liked, well-known, or frequently chosen by a particular audience, group, or context.
- 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_69e75db9b964819096802dcf502e577e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f7555c688190b28c0de18902fdbe |
completed | May 2, 2026, 1:08 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 2:26 p.m.