Triple
T10694745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rivington Pike |
E252104
|
entity |
| Predicate | accessibleFrom |
P1985
|
FINISHED |
| Object | Rivington village |
E187559
|
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: Rivington village | Statement: [Rivington Pike, accessibleFrom, Rivington village]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rivington village Context triple: [Rivington Pike, accessibleFrom, Rivington village]
-
A.
Rivington
chosen
Rivington is a rural village in Lancashire, England, known for its scenic moorland landscapes, reservoirs, and historic gardens.
-
B.
Rastrick
Rastrick is a village and residential area in West Yorkshire, England, forming part of the town of Brighouse.
-
C.
Rivington services
Rivington services is a motorway service area in North West England that provides facilities for drivers traveling on the M61.
-
D.
Collyhurst
Collyhurst is an inner-city district of Manchester, England, known historically for its red sandstone quarries and working-class residential character.
-
E.
West End village
West End village is a small settlement in Surrey, England, known for its proximity to West End Common and its semi-rural character.
- 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_69d6aa5bd7c08190a816e733b4045c23 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fd39c3788190bb7cd0acf8b6efdd |
completed | April 9, 2026, 1:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69dbad00f7c8819097566994307c4550 |
completed | April 12, 2026, 2:32 p.m. |
Created at: April 8, 2026, 9:11 p.m.