Triple
T29861390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Exiles |
E758326
|
entity |
| Predicate | hasFanChantReference |
P15355
|
FINISHED |
| Object | Newport County supporters’ songs |
—
|
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: Newport County supporters’ songs | Statement: [The Exiles, hasFanChantReference, Newport County supporters’ songs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFanChantReference Context triple: [The Exiles, hasFanChantReference, Newport County supporters’ songs]
-
A.
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.
-
B.
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.
-
C.
inspiredFanChant
Indicates that one entity created, led, or motivated a fan chant in response to or in admiration of another entity.
-
D.
hasChant
chosen
Indicates that an entity is associated with or characterized by a particular chant.
-
E.
hasFanTributeUse
Indicates that something is used, referenced, or incorporated within a fan-created tribute to a work, person, or entity.
- 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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: April 29, 2026, 5:49 p.m.