Triple
T8216069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hungerford Town F.C. |
E191934
|
entity |
| Predicate | homeStadium |
P890
|
FINISHED |
| Object | Bulpit Lane |
E755636
|
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: Bulpit Lane | Statement: [Hungerford Town F.C., homeStadium, Bulpit Lane]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bulpit Lane Context triple: [Hungerford Town F.C., homeStadium, Bulpit Lane]
-
A.
Bulpit Lane
chosen
Bulpit Lane is a football ground in Hungerford, England, best known as the home stadium of Hungerford Town F.C.
-
B.
Coldhams Lane
Coldhams Lane is a road in Cambridge, England, that serves as a key local route connecting residential and commercial areas in the eastern part of the city.
-
C.
Cudham Lane
Cudham Lane is a local road serving the rural village of Cudham in the London Borough of Bromley, England.
-
D.
Woodhouse Lane
Woodhouse Lane is a major road in Leeds, West Yorkshire, serving as a key route between the city centre and the university and Hyde Park areas.
-
E.
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.
- 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_69ca82c8c054819087fedd9a5436b8a3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb776dcfa08190969863b886336c91 |
completed | March 31, 2026, 7:27 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf5120159881908361bf9cb81e3932 |
completed | April 3, 2026, 5:33 a.m. |
Created at: March 30, 2026, 5:44 p.m.