Triple
T31870929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dover-Foxcroft, Maine |
E813593
|
entity |
| Predicate | distanceToBangor |
P6905
|
FINISHED |
| Object | approximately 35 miles northwest |
—
|
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 35 miles northwest | Statement: [Dover-Foxcroft, Maine, distanceToBangor, approximately 35 miles northwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToBangor Context triple: [Dover-Foxcroft, Maine, distanceToBangor, approximately 35 miles northwest]
-
A.
distanceToBangorMaine
chosen
Indicates the spatial distance between a given entity or location and Bangor, Maine.
-
B.
distanceFromBoston
Indicates the spatial distance between a given entity’s location and the city of Boston.
-
C.
distanceToProvidence
Indicates the measured spatial distance between a given entity’s location and the location of Providence.
-
D.
distanceToWorcester
Indicates the measured distance between a given entity’s location and the city of Worcester.
-
E.
distanceToHartford
Indicates the spatial distance between a given entity’s location and the city of Hartford.
- F. None of above.
Provenance (3 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_69f348ecb07481909c8f72619131b115 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a023f290e3081909a465d6cfb79518a |
completed | May 11, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_6a0238d1436c8190ab0251030b01902e |
completed | May 11, 2026, 8:15 p.m. |
Created at: April 30, 2026, 11:54 p.m.