Triple
T7267495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hawkhurst |
E161013
|
entity |
| Predicate | distanceToRoyalTunbridgeWells |
P73240
|
FINISHED |
| Object | approximately 15 miles south-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 15 miles south-east | Statement: [Hawkhurst, distanceToRoyalTunbridgeWells, approximately 15 miles south-east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToRoyalTunbridgeWells Context triple: [Hawkhurst, distanceToRoyalTunbridgeWells, approximately 15 miles south-east]
-
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.
distanceToCanterbury
Indicates the spatial distance between a given entity’s location and the location of Canterbury.
-
D.
distanceToWhitchurch
Indicates the spatial distance between a given entity and the location named Whitchurch.
-
E.
distanceToFolkestone
Indicates the spatial distance between a given location or entity and the town of Folkestone.
- 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_69c6885181008190b419040e22939c7c |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb088dac8190b353f6ea3d686025 |
completed | March 27, 2026, 8:39 p.m. |
| PD | Predicate disambiguation | batch_69c6e76876608190ac4652bc7153302e |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:58 p.m.