Triple
T8419612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Village of Dolgeville, New York |
E198814
|
entity |
| Predicate | isBorderSettlementOf |
P46520
|
FINISHED |
| Object | Herkimer County, New York |
—
|
NE NERFINISHED |
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: Herkimer County, New York | Statement: [Village of Dolgeville, New York, isBorderSettlementOf, Herkimer County, New York]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBorderSettlementOf Context triple: [Village of Dolgeville, New York, isBorderSettlementOf, Herkimer County, New York]
-
A.
isBorderMunicipality
Indicates that a municipality is located on or directly adjacent to the border of a larger administrative region, country, or jurisdiction.
-
B.
hasBorderCity
Indicates that one location is a city situated on or very near the border of another geographic or political region.
-
C.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
D.
borderSettlement
chosen
Indicates that a settlement is located near or along a political or administrative border.
-
E.
borderStateOf
Indicates that one state shares a common boundary or border with another state.
- 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_69ca8312d63c8190bf133b676b44a385 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb84c941988190884a5c0cbb44bcc2 |
completed | March 31, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69cb70d70ea081909c3dc1bd2ec14f85 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:06 p.m.