Triple
T16038497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Lancashire Road |
E389028
|
entity |
| Predicate | passesThrough |
P225
|
FINISHED |
| Object | Leigh |
E59813
|
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: Leigh | Statement: [East Lancashire Road, passesThrough, Leigh]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Leigh Context triple: [East Lancashire Road, passesThrough, Leigh]
-
A.
Leigh
Leigh is a village and civil parish in the Malvern Hills district of Worcestershire, England.
-
B.
Leigh
Leigh is a given name and surname of English origin, used for all genders and often considered a variant spelling of "Lee."
-
C.
Leigh
chosen
Leigh is a parliamentary constituency in Greater Manchester, England, historically represented in the UK House of Commons.
-
D.
Birkenhead
Birkenhead is a town in north west England, situated on the Wirral Peninsula across the River Mersey from Liverpool, known historically for its shipbuilding and docks.
-
E.
Birkenhead
Birkenhead is a suburb of Adelaide in South Australia, known for its proximity to the Port River and maritime and industrial heritage.
- 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_69d86dada3808190825d5f80d72fbe88 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1833eb90c8190b10dca3ce0793ddf |
completed | April 17, 2026, 12:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffdbd5acb48190a10e40074fffd425 |
completed | May 10, 2026, 1:13 a.m. |
Created at: April 10, 2026, 4:56 a.m.