Triple
T31068247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashurst |
E791735
|
entity |
| Predicate | distanceFromRoyalTunbridgeWells |
P73240
|
FINISHED |
| Object | approximately 4–5 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 4–5 miles southwest | Statement: [Ashurst, distanceFromRoyalTunbridgeWells, approximately 4–5 miles southwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromRoyalTunbridgeWells Context triple: [Ashurst, distanceFromRoyalTunbridgeWells, approximately 4–5 miles southwest]
-
A.
distanceTo Royal Tunbridge Wells
chosen
Indicates the spatial distance between a given reference point and the location of Royal Tunbridge Wells.
-
B.
distanceTo Tonbridge
Indicates the spatial distance between a given reference point and the location of Tonbridge.
-
C.
distanceToBridgwater
Indicates the spatial distance between a given entity and the location named Bridgwater.
-
D.
distanceToLeatherhead
Indicates the spatial distance between a given entity and the location known as Leatherhead.
-
E.
distanceToMaidstone
Indicates the spatial distance between a given entity and the location Maidstone.
- 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_69f224cc0c5c81908404f087bff92997 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a019d1407588190b3b9b83fca2e61fe |
completed | May 11, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_6a019c760e3081909cfe9c0603727e48 |
completed | May 11, 2026, 9:08 a.m. |
Created at: April 29, 2026, 9:01 p.m.