Triple
T37884944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rammer Jammer cheer |
E944970
|
entity |
| Predicate | hasChantLine |
P15355
|
FINISHED |
| Object | Rammer Jammer Yellow Hammer, give ’em hell, Alabama |
—
|
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: Rammer Jammer Yellow Hammer, give ’em hell, Alabama | Statement: [Rammer Jammer cheer, hasChantLine, Rammer Jammer Yellow Hammer, give ’em hell, Alabama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChantLine Context triple: [Rammer Jammer cheer, hasChantLine, Rammer Jammer Yellow Hammer, give ’em hell, Alabama]
-
A.
hasChant
chosen
Indicates that an entity is associated with or characterized by a particular chant.
-
B.
hasChantLikeChorus
Indicates that one element features or is characterized by a chorus section that is chant-like in style or delivery.
-
C.
hasChantLikeSections
Indicates that something contains portions that resemble or function like chants in style, rhythm, or delivery.
-
D.
hasChantingStyle
Indicates that an entity is associated with or characterized by a particular style or manner of chanting.
-
E.
hasSungChorus
Indicates that an entity has performed or participated in singing the chorus section of a 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_69f76ef02668819089e7940c4001af5e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff49016dcc8190a8a43868c728b4f1 |
completed | May 9, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_69ff4891924c8190b5be340e2520e012 |
completed | May 9, 2026, 2:45 p.m. |
Created at: May 3, 2026, 4:19 p.m.