Triple
T468239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ramsbottom |
E8495
|
entity |
| Predicate | distanceFromBury |
P7750
|
FINISHED |
| Object | approximately 4 miles northwest of Bury |
—
|
LITERAL 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: approximately 4 miles northwest of Bury | Statement: [Ramsbottom, distanceFromBury, approximately 4 miles northwest of Bury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromBury Context triple: [Ramsbottom, distanceFromBury, approximately 4 miles northwest of Bury]
-
A.
distanceFromTerminus
Indicates the measured distance of an entity from a defined endpoint or terminus along a route, path, or sequence.
-
B.
burialPlace
Indicates the location where a person or entity is buried.
-
C.
distance
chosen
Indicates the spatial separation or length between two points, objects, or locations.
-
D.
burialCoordinates
Indicates the geographic location where an entity is buried, typically expressed as spatial coordinates.
-
E.
distanceFromDowntown
Indicates the physical distance between a given location and the central downtown area.
- F. None of above.
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_69a2e7f3aeb48190a19453e3a043f486 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efd9bea081909ee782840f3da12b |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2edebb3988190907992a584b4e260 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.