Triple
T14844348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wimborne Minster |
E349046
|
entity |
| Predicate | distanceFromPoole |
P116052
|
FINISHED |
| Object | approximately 5 miles north |
—
|
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 | Statement: [Wimborne Minster, distanceFromPoole, approximately 5 miles north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromPoole Context triple: [Wimborne Minster, distanceFromPoole, approximately 5 miles north]
-
A.
distanceFromLeeds
Indicates the spatial distance between a given entity and the location of Leeds.
-
B.
distanceToBridgwater
Indicates the spatial distance between a given entity and the location named Bridgwater.
-
C.
distanceFromWokingham
Indicates the measured distance between a given entity or location and Wokingham.
-
D.
distanceToBasingstoke
Indicates the spatial distance between a given entity and the location of Basingstoke.
-
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_69d822ec69008190a9232caa68836872 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded291103c8190a64cfe700bfee197 |
completed | April 14, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69de8c13418c819088ff9905ace1416a |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de90806f3881908fcbfec5bd4ab4d2 |
completed | April 14, 2026, 7:07 p.m. |
Created at: April 10, 2026, 1:53 a.m.