Triple
T23710278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cockermouth Rugby Club |
E585840
|
entity |
| Predicate | homeMatches |
P8186
|
FINISHED |
| Object | Cockermouth |
—
|
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: Cockermouth | Statement: [Cockermouth Rugby Club, homeMatches, Cockermouth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeMatches Context triple: [Cockermouth Rugby Club, homeMatches, Cockermouth]
-
A.
homeMatchesCountry
Indicates that an entity’s home location is situated within the specified country.
-
B.
homeMatchesWatched
Indicates that the number or set of home matches corresponds to those that have been watched.
-
C.
hostedHomeMatchesFor
Indicates that an entity organized and held competitive matches at its own home venue for another entity or group.
-
D.
playedHomeMatchesIn
chosen
Indicates that an entity (typically a sports team) hosted its home matches at a specified venue or location.
-
E.
supportsHomeMatchesOf
Indicates that one entity provides backing, resources, or assistance specifically for the home matches of 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_69e24905f77881908194d645676acd60 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b776d21c8190af48958e1b14aa4c |
completed | April 29, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:53 p.m.