Triple
T26869097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sturry |
E676556
|
entity |
| Predicate | distanceFromCanterbury |
P37133
|
FINISHED |
| Object | approximately 3 miles northeast |
—
|
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 3 miles northeast | Statement: [Sturry, distanceFromCanterbury, approximately 3 miles northeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromCanterbury Context triple: [Sturry, distanceFromCanterbury, approximately 3 miles northeast]
-
A.
distanceToCanterbury
chosen
Indicates the spatial distance between a given entity’s location and the location of Canterbury.
-
B.
directionFromCanterbury
Indicates the spatial direction in which one entity lies relative to Canterbury.
-
C.
distanceToFolkestone
Indicates the spatial distance between a given location or entity and the town of Folkestone.
-
D.
distanceToMaidstone
Indicates the spatial distance between a given entity and the location Maidstone.
-
E.
distanceToChichester
Indicates the measured distance between a given location or entity and the place Chichester.
- 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_69eee9ba94bc8190b44c5d4397d04ecd |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69fed83b1d188190a318b0ad3003200a |
completed | May 9, 2026, 6:46 a.m. |
| PD | Predicate disambiguation | batch_69fed78e03548190b6e6ad93ae8d131d |
completed | May 9, 2026, 6:43 a.m. |
Created at: April 27, 2026, 5:30 a.m.