Triple
T26662512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurlford |
E666685
|
entity |
| Predicate | hasJuniorFootballClub |
P59846
|
FINISHED |
| Object | Hurlford United F.C. |
—
|
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: Hurlford United F.C. | Statement: [Hurlford, hasJuniorFootballClub, Hurlford United F.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasJuniorFootballClub Context triple: [Hurlford, hasJuniorFootballClub, Hurlford United F.C.]
-
A.
hostsFootballClub
chosen
Indicates that one entity serves as the home location or venue where a football club is based or plays its matches.
-
B.
foundedFootballClub
Indicates that a person or entity established or created a particular football club.
-
C.
associationFootballClub
Indicates that the subject is an association football (soccer) club, i.e., an organized team entity that plays the sport of association football.
-
D.
nearFootballClub
Indicates that one entity is located close to, or in the immediate vicinity of, a football club.
-
E.
hasFootballTrainingCentre
Indicates that an entity possesses or hosts a facility specifically designated for football training.
- 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_69ee9cf8c7188190b9b00270a8a89164 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f616c0a7bc8190bb57f83858b4f7fb |
completed | May 2, 2026, 3:22 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 2:37 a.m.