Triple
T8652644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peterlee |
E205135
|
entity |
| Predicate | distanceToSunderland |
P62159
|
FINISHED |
| Object | approximately 11 miles south of Sunderland |
—
|
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 11 miles south of Sunderland | Statement: [Peterlee, distanceToSunderland, approximately 11 miles south of Sunderland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToSunderland Context triple: [Peterlee, distanceToSunderland, approximately 11 miles south of Sunderland]
-
A.
distanceFromSunderland
chosen
Indicates the spatial distance between a given entity and the location of Sunderland.
-
B.
distanceToSunderland_km
Indicates the physical distance, measured in kilometers, between a given place and Sunderland.
-
C.
distanceFromNewcastle
Indicates the spatial distance between a given entity or location and the city of Newcastle.
-
D.
distanceToManchester
Indicates the measured or calculated distance between a given entity’s location and the city of Manchester.
-
E.
distanceToClitheroe
Indicates the spatial distance between a given entity or location and the town of Clitheroe.
- 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_69ca834e56848190abb0eeaec9dedd32 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc484051b48190b1d0cc63426c204d |
completed | March 31, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69cc45619460819091e83ffdec99c865 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:29 p.m.