Triple
T1509843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rothbury |
E33988
|
entity |
| Predicate | distanceFromAlnwick |
P29382
|
FINISHED |
| Object | approximately 13 miles southwest |
—
|
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 13 miles southwest | Statement: [Rothbury, distanceFromAlnwick, approximately 13 miles southwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromAlnwick Context triple: [Rothbury, distanceFromAlnwick, approximately 13 miles southwest]
-
A.
distanceFromNewcastle
Indicates the spatial distance between a given entity or location and the city of Newcastle.
-
B.
distanceFromNorwich
Indicates the measured distance between a given place or object and the location of Norwich.
-
C.
distanceFromEdinburghApprox
Indicates that an entity is located at an approximate distance from Edinburgh, rather than an exact measured distance.
-
D.
distanceToCarlisle
Indicates the spatial distance between a given entity or location and Carlisle.
-
E.
distanceToManchester
Indicates the measured or calculated distance between a given entity’s location and the city of Manchester.
- 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_69a885f352a4819099b24ff15489dede |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a8e2dd93dc8190a78443900e8d5564 |
completed | March 5, 2026, 1:56 a.m. |
| PD | Predicate disambiguation | batch_69a88728c150819095cdcdbfcabf4249 |
completed | March 4, 2026, 7:25 p.m. |
| PDg | Predicate description generation | batch_69a8e2dbc848819084eb0d50189fa967 |
completed | March 5, 2026, 1:56 a.m. |
Created at: March 4, 2026, 7:24 p.m.