Triple
T28486718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Bannsiders |
E720848
|
entity |
| Predicate | homeGroundOfAssociatedClub |
P164581
|
FINISHED |
| Object | The Showgrounds, Coleraine |
—
|
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: The Showgrounds, Coleraine | Statement: [The Bannsiders, homeGroundOfAssociatedClub, The Showgrounds, Coleraine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeGroundOfAssociatedClub Context triple: [The Bannsiders, homeGroundOfAssociatedClub, The Showgrounds, Coleraine]
-
A.
locatedAtStadiumOfClub
Indicates that something is situated in the stadium that belongs to or is used by a particular sports club.
-
B.
homeGroundAlternateName
Indicates that an alternative or secondary name is used to refer to a particular home ground.
-
C.
previousHomeGroundLocatedIn
Indicates that the location specified is where an entity’s former or earlier home ground was situated.
-
D.
primaryHomeGroundNot
Indicates that the specified location is explicitly not the entity’s primary home ground.
-
E.
homeLeagueClub
Indicates that a club competes in or is affiliated with a particular home league.
- F. None of above. chosen
Provenance (4 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_69f01a5a47148190b0a7e111bc432e0a |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f64f1072108190b52d8c1665e3b071 |
completed | May 2, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64db8ee1881909362701d72ffe282 |
completed | May 2, 2026, 7:17 p.m. |
Created at: April 28, 2026, 2:58 a.m.