Triple
T30982005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parbold |
E789401
|
entity |
| Predicate | distanceToOrmskirk |
P203461
|
FINISHED |
| Object | approximately 6 miles east |
—
|
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 6 miles east | Statement: [Parbold, distanceToOrmskirk, approximately 6 miles east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToOrmskirk Context triple: [Parbold, distanceToOrmskirk, approximately 6 miles east]
-
A.
distanceToClitheroe
Indicates the spatial distance between a given entity or location and the town of Clitheroe.
-
B.
distanceFromSunderland
Indicates the spatial distance between a given entity and the location of Sunderland.
-
C.
distanceToSunderland_km
Indicates the physical distance, measured in kilometers, between a given place and Sunderland.
-
D.
distanceToKeswick
Indicates the spatial distance between a given entity and the location named Keswick.
-
E.
distanceToCockermouth
Indicates the measured or specified distance between a given entity or location and Cockermouth.
- F. None of above. chosen
Provenance (4 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_69f224c4831c8190be53924ec25a150a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a0186cde2fc819080d7c06503dcc479 |
completed | May 11, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_6a0183ff6d34819080c8ad7c11611a36 |
completed | May 11, 2026, 7:23 a.m. |
| PDg | Predicate description generation | batch_6a0186cd171081908451bfb66aa014ba |
completed | May 11, 2026, 7:35 a.m. |
Created at: April 29, 2026, 8:55 p.m.