Triple
T22070173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aspatria |
E545384
|
entity |
| Predicate | distanceToWorkington |
P146498
|
FINISHED |
| Object | approximately 8 miles |
—
|
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 8 miles | Statement: [Aspatria, distanceToWorkington, approximately 8 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToWorkington Context triple: [Aspatria, distanceToWorkington, approximately 8 miles]
-
A.
distanceToWindsor
Indicates the spatial distance between a given entity and the location named Windsor.
-
B.
distanceToWinnipeg
Indicates the spatial distance between a given entity’s location and the city of Winnipeg.
-
C.
distanceToKingstonApprox
Indicates an approximate distance between a given location and Kingston.
-
D.
distanceToWakefield
Indicates the measured or calculated distance between a given entity’s location and the location of Wakefield.
-
E.
distanceFromFortWilliam
Indicates the measured distance between an entity and Fort William.
- 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_69e11e344dfc81909b1d88a7221329c7 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128881af481909b28cda2d343f4e3 |
completed | April 28, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69e6f64a6a70819089d1a6c3a2384861 |
completed | April 21, 2026, 4 a.m. |
| PDg | Predicate description generation | batch_69e6fad4a540819096cdd5ea08527220 |
completed | April 21, 2026, 4:19 a.m. |
Created at: April 16, 2026, 8:28 p.m.