Triple
T8662234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turners Hill |
E205574
|
entity |
| Predicate | distanceToEastGrinstead |
P83954
|
FINISHED |
| Object | approximately 6 miles south-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 6 miles south-west | Statement: [Turners Hill, distanceToEastGrinstead, approximately 6 miles south-west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToEastGrinstead Context triple: [Turners Hill, distanceToEastGrinstead, approximately 6 miles south-west]
-
A.
distanceToStevenage
Indicates the spatial distance between a given entity or location and Stevenage.
-
B.
distanceToEgham
Indicates the spatial distance between a given entity and the location of Egham.
-
C.
distanceToFolkestone
Indicates the spatial distance between a given location or entity and the town of Folkestone.
-
D.
distanceToBrighton
Indicates the measured or specified distance between a given entity or location and Brighton.
-
E.
distanceToHorley
Indicates the spatial distance between a given entity and the location named Horley.
- 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_69ca83516ae88190aefe034b3bc589e3 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4872a190819087d679f3006bd030 |
completed | March 31, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69cc4564e018819081036722f3e42a71 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc46c330bc8190a9b644078881c6ff |
completed | March 31, 2026, 10:12 p.m. |
Created at: March 30, 2026, 6:30 p.m.