Triple
T5020916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asthall |
E112845
|
entity |
| Predicate | distanceToBurford |
P61575
|
FINISHED |
| Object | approximately 3 miles east |
—
|
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 east | Statement: [Asthall, distanceToBurford, approximately 3 miles east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToBurford Context triple: [Asthall, distanceToBurford, approximately 3 miles east]
-
A.
distanceFromBathurst
Indicates the spatial distance between a given entity and the reference location Bathurst.
-
B.
distanceToHartford
Indicates the spatial distance between a given entity’s location and the city of Hartford.
-
C.
distanceToFortCollins
Indicates the spatial distance between a given entity’s location and the city of Fort Collins.
-
D.
distanceFromHuntingdon
Indicates the spatial distance between a given entity and the location of Huntingdon.
-
E.
distanceToBawtry
Indicates the spatial distance between a given entity and the location of Bawtry.
- 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_69bd4435c2f48190be593158cbfcf8a3 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd736399ac8190aa38efc4b4edc6a2 |
completed | March 20, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69bd714ecfe08190b5830cfc1c74fa17 |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd72e1b7cc8190b2e621fdf8f22e38 |
completed | March 20, 2026, 4:16 p.m. |
Created at: March 20, 2026, 1:36 p.m.