Triple
T19237502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Village of Dansville |
E481036
|
entity |
| Predicate | distanceToRochesterNY |
P135298
|
FINISHED |
| Object | approximately 50 miles south |
—
|
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 50 miles south | Statement: [Village of Dansville, distanceToRochesterNY, approximately 50 miles south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToRochesterNY Context triple: [Village of Dansville, distanceToRochesterNY, approximately 50 miles south]
-
A.
distanceToSyracuse
Indicates the spatial distance between a given entity’s location and the location of Syracuse.
-
B.
distanceToNewYorkCity
Indicates the spatial distance between a given entity’s location and New York City.
-
C.
distanceToUtica
Indicates the spatial distance between a given location or object and the place named Utica.
-
D.
directionFromRochester
Indicates the compass direction or relative bearing of one place or object as measured outward starting from Rochester.
-
E.
distanceToAlbanyNewYork
Indicates the spatial distance between a given location and Albany, New York.
- 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_69d8e8ccb8f48190ad420098e74fb1db |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5faee7324819090a4c56147cb0bf5 |
completed | April 20, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e4dcfae6f081909cc173cf71a5005c |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4debc39ac81908b7c5ef797046360 |
completed | April 19, 2026, 1:55 p.m. |
Created at: April 10, 2026, 1:26 p.m.