Triple
T22490340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Country derby |
E555998
|
entity |
| Predicate | hasDerogatoryChanting |
P148419
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Black Country derby, hasDerogatoryChanting, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDerogatoryChanting Context triple: [Black Country derby, hasDerogatoryChanting, yes]
-
A.
hasChant
Indicates that an entity is associated with or characterized by a particular chant.
-
B.
hasSpokenChants
Indicates that an entity has uttered or recited ritualistic or formulaic chants, typically as part of a ceremonial, religious, or magical practice.
-
C.
hasFanChantPotential
Indicates that something (such as a song, phrase, or performance element) is well-suited to be adopted and enthusiastically chanted by a crowd or fanbase.
-
D.
fanChant
Indicates a relationship where a group of fans collectively chant or vocalize in support of, or in response to, a person, team, or performance.
-
E.
hasChantLikeChorus
Indicates that one element features or is characterized by a chorus section that is chant-like in style or delivery.
- 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_69e11e53897c819088863779f8c50bb0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15c40930c81908310ac6afd98c62e |
completed | April 29, 2026, 1:17 a.m. |
| PD | Predicate disambiguation | batch_69e898b6eee08190ba673a0ee329e671 |
completed | April 22, 2026, 9:45 a.m. |
| PDg | Predicate description generation | batch_69e8aa3b4c288190951cca06d42bea51 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:49 p.m.