Triple
T3353386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A59 road |
E70547
|
entity |
| Predicate | connectsTown |
P845
|
FINISHED |
| Object | Burscough |
E225993
|
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: Burscough | Statement: [A59 road, connectsTown, Burscough]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Burscough Context triple: [A59 road, connectsTown, Burscough]
-
A.
Burscough
chosen
Burscough is a village in West Lancashire, England, known for its historic canalside setting and agricultural surroundings.
-
B.
Buckland
Buckland is a small Inupiat community and city in northwestern Alaska situated along the Buckland River.
-
C.
Buckland
Buckland is a small historic community located within the Bull Run Mountains region of northern Virginia.
-
D.
Queenborough
Queenborough is a small historic port town in Kent, England, situated on the Isle of Sheppey and known for its maritime heritage and medieval origins.
-
E.
Grundisburgh
Grundisburgh is a village and civil parish in the English county of Suffolk, known for its rural character and historic parish church.
- 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_69ad85a4ef7c8190a29e2bbd6fa454e4 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb23ec53881908a04c7f784fe8c43 |
completed | March 8, 2026, 5:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b32532ebd08190bf174d72fba89a75 |
completed | March 12, 2026, 8:42 p.m. |
Created at: March 8, 2026, 3:13 p.m.