Triple
T9974923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bury FC |
E196302
|
entity |
| Predicate | homeGround |
P890
|
FINISHED |
| Object | Gigg Lane |
E261249
|
NE 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: Gigg Lane | Statement: [Bury FC, homeGround, Gigg Lane]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gigg Lane Context triple: [Bury FC, homeGround, Gigg Lane]
-
A.
Gigg Lane
chosen
Gigg Lane is a historic football stadium in Bury, Greater Manchester, long associated with Bury F.C. and known as one of the oldest professional football grounds in the world.
-
B.
Sheepfoot Lane
Sheepfoot Lane is a local road in the Heaton Park area of Manchester, England, providing access around the park and nearby residential districts.
-
C.
Butt Lane
Butt Lane is a suburban area within the town of Kidsgrove in Staffordshire, England.
-
D.
Bulpit Lane
Bulpit Lane is a football ground in Hungerford, England, best known as the home stadium of Hungerford Town F.C.
-
E.
Easington Lane
Easington Lane is a village in the City of Sunderland, Tyne and Wear, in North East England.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca82eea2b88190a0e511d21a31f386 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb849da448190b826cb8fbf2eeb89 |
completed | April 2, 2026, 12:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d3000b21088190aa3ebb2ccbce9a6e |
completed | April 6, 2026, 12:36 a.m. |
Created at: March 30, 2026, 8:48 p.m.