Triple
T6194729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grosmont |
E138480
|
entity |
| Predicate | distanceToWhitby |
P69589
|
FINISHED |
| Object | approximately 6 miles southwest |
—
|
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 southwest | Statement: [Grosmont, distanceToWhitby, approximately 6 miles southwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToWhitby Context triple: [Grosmont, distanceToWhitby, approximately 6 miles southwest]
-
A.
distanceToKeswick
Indicates the spatial distance between a given entity and the location named Keswick.
-
B.
distanceToHunstanton
Indicates the measured spatial distance between a given entity and the location Hunstanton.
-
C.
distanceToBerwickUponTweed
Indicates the spatial distance between a given entity and the location of Berwick-upon-Tweed.
-
D.
distanceToLondon
Indicates the measured distance between a given entity’s location and the city of London.
-
E.
distanceToFolkestone
Indicates the spatial distance between a given location or entity and the town of Folkestone.
- 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_69c008ab9b3081908a11b2c744838435 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062443cec81909dc9bafea2f5e7d4 |
completed | March 22, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c055fbce1081908805fd12e242ab96 |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c056c87340819088003f427706ebf8 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:19 p.m.