Triple
T15986747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castle Ashby |
E387714
|
entity |
| Predicate | distanceFromWellingborough |
P121189
|
FINISHED |
| Object | approximately 5 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 5 miles south-west | Statement: [Castle Ashby, distanceFromWellingborough, approximately 5 miles south-west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromWellingborough Context triple: [Castle Ashby, distanceFromWellingborough, approximately 5 miles south-west]
-
A.
distanceToWymondham
Indicates the spatial distance between a given entity or location and Wymondham.
-
B.
distanceFromTamworth
Indicates the spatial distance measured from the reference location Tamworth to another place or entity.
-
C.
distanceToWisbech
Indicates the spatial distance between a given location or entity and the town of Wisbech.
-
D.
distanceToTelford
Indicates the spatial distance between a given entity and the location of Telford.
-
E.
distanceFromWatfordJunction
Indicates the spatial distance between a given location and Watford Junction.
- 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_69d86daa562c81908aacc179c0fe8fb5 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4e871c819082d7b1c1eaf5b4fe |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d9d8e881909b559a3e3ca21d24 |
completed | April 16, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69e17d48cc9c8190b03fd07ae2e9dfd8 |
completed | April 17, 2026, 12:22 a.m. |
Created at: April 10, 2026, 4:54 a.m.