Triple
T17690547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rochford |
E441013
|
entity |
| Predicate | distanceFromSouthend-on-Sea |
P121451
|
FINISHED |
| Object | approximately 3 miles north of Southend-on-Sea |
—
|
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 north of Southend-on-Sea | Statement: [Rochford, distanceFromSouthend-on-Sea, approximately 3 miles north of Southend-on-Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromSouthend-on-Sea Context triple: [Rochford, distanceFromSouthend-on-Sea, approximately 3 miles north of Southend-on-Sea]
-
A.
distanceToSouthend-on-Sea
chosen
Indicates the spatial distance between a given entity and the location Southend-on-Sea.
-
B.
distanceToFolkestone
Indicates the spatial distance between a given location or entity and the town of Folkestone.
-
C.
distanceToSouthampton
Indicates the measured distance between a given entity’s location and the location of Southampton.
-
D.
distanceToBasildon
Indicates the spatial distance between a given entity and the location of Basildon.
-
E.
distanceToLymington
Indicates the spatial distance between a given entity and the location of Lymington.
- 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4704b43a88190ba29654ca695839e |
completed | April 19, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69e3cde3673c8190a889e14ba1f07dc1 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 10:03 a.m.