Triple
T32121806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Halden |
E820395
|
entity |
| Predicate | distanceToTenterden |
P204103
|
FINISHED |
| Object | approximately 5 miles north-west |
—
|
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 5 miles north-west | Statement: [High Halden, distanceToTenterden, approximately 5 miles north-west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToTenterden Context triple: [High Halden, distanceToTenterden, approximately 5 miles north-west]
-
A.
distanceToFolkestone
Indicates the spatial distance between a given location or entity and the town of Folkestone.
-
B.
distanceToDartford
Indicates the spatial distance between a given entity and the location of Dartford.
-
C.
distanceToMaidstone
Indicates the spatial distance between a given entity and the location Maidstone.
-
D.
distanceToSouthend-on-Sea
Indicates the spatial distance between a given entity and the location Southend-on-Sea.
-
E.
distanceToPenzance
Indicates the spatial distance between a given entity’s location and the town of Penzance.
- 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_69f34902d42c819083a8e6bba9a8bb9a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a0324c2d618819093f7e6424b0f5baf |
completed | May 12, 2026, 1:01 p.m. |
| PD | Predicate disambiguation | batch_6a0324292e588190b37d0c3016ea2062 |
completed | May 12, 2026, 12:59 p.m. |
| PDg | Predicate description generation | batch_6a0324c1f89881909fc713e93e9c5f1c |
completed | May 12, 2026, 1:01 p.m. |
Created at: May 1, 2026, 12:28 a.m.