Triple
T18327204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sidestrand |
E439041
|
entity |
| Predicate | distanceToCromer |
P130773
|
FINISHED |
| Object | approximately 3 miles southeast |
—
|
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 3 miles southeast | Statement: [Sidestrand, distanceToCromer, approximately 3 miles southeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToCromer Context triple: [Sidestrand, distanceToCromer, approximately 3 miles southeast]
-
A.
distanceToHunstanton
Indicates the measured spatial distance between a given entity and the location Hunstanton.
-
B.
distanceToSwaffham
Indicates the spatial distance between a given entity and the location Swaffham.
-
C.
distanceFromMorecambe
Indicates the measured or specified distance between a given entity and the location of Morecambe.
-
D.
distanceToFolkestone
Indicates the spatial distance between a given location or entity and the town of Folkestone.
-
E.
distanceFromDover
Indicates the measured distance between a given entity or location and the place named Dover.
- 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50aab3e7c81909b1c0a688707dfd6 |
completed | April 19, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69e44fe4ee10819086b4142444fca1f5 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a1bda48190a9cd1db436d4be62 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:36 a.m.