Triple
T24573919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hever, Kent |
E608045
|
entity |
| Predicate | distanceToEdenbridge |
P156396
|
FINISHED |
| Object | about 3 miles |
—
|
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: about 3 miles | Statement: [Hever, Kent, distanceToEdenbridge, about 3 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToEdenbridge Context triple: [Hever, Kent, distanceToEdenbridge, about 3 miles]
-
A.
distanceToBridgwater
Indicates the spatial distance between a given entity and the location named Bridgwater.
-
B.
distanceToClevedon
Indicates the measured or specified distance between a given entity and the location Clevedon.
-
C.
distanceToBodmin
Indicates the spatial distance between an entity and the location Bodmin.
-
D.
distanceToSouthend-on-Sea
Indicates the spatial distance between a given entity and the location Southend-on-Sea.
-
E.
distanceFromPortElizabeth_km
Indicates the distance, measured in kilometers, between a given location and Port Elizabeth.
- 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_69e2c4cdab6c8190aae6e5d3de55c95e |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a92791988190a0dff0a6f9e770e8 |
completed | April 30, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
| PDg | Predicate description generation | batch_69f2a846c5bc81909ba50cee483bea91 |
completed | April 30, 2026, 12:54 a.m. |
Created at: April 18, 2026, 2:28 a.m.