Triple
T25566189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enfield Town F.C. |
E640841
|
entity |
| Predicate | hasSupporterTrust |
P3508
|
FINISHED |
| Object | Enfield Town Supporters Society |
—
|
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: Enfield Town Supporters Society | Statement: [Enfield Town F.C., hasSupporterTrust, Enfield Town Supporters Society]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSupporterTrust Context triple: [Enfield Town F.C., hasSupporterTrust, Enfield Town Supporters Society]
-
A.
hasSupporter
Indicates that one entity supports, endorses, or backs another entity.
-
B.
hasSupporterDetail
Indicates that an entity is associated with specific information or attributes about a supporter related to it.
-
C.
hasTrust
Indicates that one entity has confidence in the reliability, integrity, or good intentions of another entity.
-
D.
hasSupporterGroup
chosen
Indicates that an entity is associated with a group of supporters that backs, promotes, or advocates for it.
-
E.
hasSupporterNickname
Indicates that an entity is associated with a nickname or informal name used specifically by its supporters or fans.
- 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_69e75dc1beb08190bac7d76b8d6e7bc4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 21, 2026, 3:49 p.m.