Triple
T22905915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poacher Line |
E568441
|
entity |
| Predicate | serves |
P98
|
FINISHED |
| Object | Ancaster |
—
|
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: Ancaster | Statement: [Poacher Line, serves, Ancaster]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ancaster Context triple: [Poacher Line, serves, Ancaster]
-
A.
Ancaster
chosen
Ancaster is a village and civil parish in the South Kesteven district of Lincolnshire, England, known for its Roman history and archaeological remains.
-
B.
Ancaster
Ancaster is a historic community and former town now incorporated into the city of Hamilton, Ontario, Canada.
-
C.
Didlington
Didlington is a small village in Norfolk, England, known for its rural landscape, historic estate, and proximity to the River Wissey.
-
D.
Morpeth
Morpeth is a historic market town in Northumberland, England, known for its traditional architecture and role as a local commercial and administrative centre.
-
E.
Uttoxeter
Uttoxeter is a historic market town in central England known for its racecourse and rural Staffordshire setting.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e2458cd9e48190943ad2e34485d939 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1801a48948190b5f51f1d02351fc7 |
completed | April 29, 2026, 3:50 a.m. |
Created at: April 17, 2026, 3:41 p.m.