Triple
T32511930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ammanford A.F.C. |
E830955
|
entity |
| Predicate | homeFans |
P136905
|
FINISHED |
| Object | residents of Ammanford and surrounding area |
—
|
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: residents of Ammanford and surrounding area | Statement: [Ammanford A.F.C., homeFans, residents of Ammanford and surrounding area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeFans Context triple: [Ammanford A.F.C., homeFans, residents of Ammanford and surrounding area]
-
A.
hasHomeFans
chosen
Indicates that a team, player, or participant is supported by fans located at their home venue or home location.
-
B.
fanAccess
Indicates that an entity has permission or the ability to access fan-related content, features, or areas associated with another entity.
-
C.
fanDestination
Indicates that one entity is the intended target or recipient of another entity’s enthusiasm, admiration, or fandom.
-
D.
fanBase1
Indicates that one entity serves as the primary or original fan base supporting another entity.
-
E.
fanBase
Indicates that one entity is the group of admirers or supporters devoted to another 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c49aa3e08190bb13ff57b2878c5d |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1 a.m.