Triple
T21952934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Torrington |
E542111
|
entity |
| Predicate | distanceToBarnstaple_km |
P146672
|
FINISHED |
| Object | approximately 19 |
—
|
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 19 | Statement: [Great Torrington, distanceToBarnstaple_km, approximately 19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToBarnstaple_km Context triple: [Great Torrington, distanceToBarnstaple_km, approximately 19]
-
A.
distanceToBodmin
Indicates the spatial distance between an entity and the location Bodmin.
-
B.
distanceTo_Aberystwyth_km
Indicates the distance, measured in kilometers, between a given entity and Aberystwyth.
-
C.
distanceToPenzance
Indicates the spatial distance between a given entity’s location and the town of Penzance.
-
D.
distanceToBridgwater
Indicates the spatial distance between a given entity and the location named Bridgwater.
-
E.
distanceFromChippenham
Indicates the spatial distance between a given entity or location and Chippenham.
- 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_69e0c47ef0e48190a50e1bcc43f4b3fd |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1243d43d8819084e280b129631288 |
completed | April 28, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e6f601f2188190893bcdde0cf58ad6 |
completed | April 21, 2026, 3:58 a.m. |
| PDg | Predicate description generation | batch_69e6fb9b75308190addc3dba7b5d5ddd |
completed | April 21, 2026, 4:22 a.m. |
Created at: April 16, 2026, 7:59 p.m.