Triple
T8059600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Bhoys |
E188085
|
entity |
| Predicate | associatedSongOrChant |
P15355
|
FINISHED |
| Object | Celtic F.C. terrace chants |
—
|
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: Celtic F.C. terrace chants | Statement: [The Bhoys, associatedSongOrChant, Celtic F.C. terrace chants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedSongOrChant Context triple: [The Bhoys, associatedSongOrChant, Celtic F.C. terrace chants]
-
A.
relatedChantOrSong
Indicates that one chant or song is associated with, derived from, or otherwise connected to another chant or song.
-
B.
alsoChantedIn
Indicates that a chant, hymn, or recitation is performed or used in an additional context, location, or tradition beyond its primary one.
-
C.
associatedWithHymns
Indicates that something has a connection or relationship to hymns, such as being used in, derived from, or thematically linked to them.
-
D.
singsAbout
Indicates that one entity performs a song whose subject or theme is another entity.
-
E.
hasChant
chosen
Indicates that an entity is associated with or characterized by a particular chant.
- 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_69ca82b2f68881908c50560697e210da |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3fcaa8b8819099267564b6542547 |
completed | March 31, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69cb049cd51c8190bb3b0f503e42fa8d |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:25 p.m.