Triple
T27860147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kop Stand |
E704202
|
entity |
| Predicate | fanBehaviour |
P130036
|
FINISHED |
| Object | coordinated 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: coordinated chants | Statement: [Kop Stand, fanBehaviour, coordinated chants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fanBehaviour Context triple: [Kop Stand, fanBehaviour, coordinated chants]
-
A.
fanInvolved
Indicates that a fan actively participates in or is directly involved with a particular event, activity, or interaction.
-
B.
fanAccess
Indicates that an entity has permission or the ability to access fan-related content, features, or areas associated with another entity.
-
C.
supporterBehavior
chosen
Indicates how a supporter acts toward, engages with, or responds to the entity or cause they are supporting.
-
D.
fanAttraction
Indicates a relationship where one entity is strongly drawn to, admires, or is devoted to another as a fan.
-
E.
fan
Indicates that one entity admires, supports, or is enthusiastically devoted to another entity, typically in a recreational or entertainment context.
- 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_69ef840e614c8190a88cf9638c14a265 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6394220d88190a9d7d5f5ebcf5e4f |
completed | May 2, 2026, 5:49 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 6:17 p.m.