Triple
T19159328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | COYI |
E469008
|
entity |
| Predicate | isRallyingChantFor |
P20424
|
FINISHED |
| Object | West Ham United supporters |
—
|
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: West Ham United supporters | Statement: [COYI, isRallyingChantFor, West Ham United supporters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRallyingChantFor Context triple: [COYI, isRallyingChantFor, West Ham United supporters]
-
A.
hasChant
Indicates that an entity is associated with or characterized by a particular chant.
-
B.
rallyingSloganOf
chosen
Indicates that a phrase or slogan is used as a unifying or motivational rallying cry associated with a particular group, movement, event, or cause.
-
C.
inspiredFanChant
Indicates that one entity created, led, or motivated a fan chant in response to or in admiration of another entity.
-
D.
isAnthemFor
Indicates that a song or musical composition serves as the official anthem representing a particular group, organization, place, or cause.
-
E.
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.
- 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_69d8dd084ff48190ac0f8c46ee722629 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5eebb573081909fcd6af8aff8692b |
completed | April 20, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b83d6881908e6271c620f74100 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:06 p.m.