Triple
T14400038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York State Route 17 |
E357045
|
entity |
| Predicate | passesNear |
P416
|
FINISHED |
| Object | Goshen, New York |
E97202
|
NE 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: Goshen, New York | Statement: [New York State Route 17, passesNear, Goshen, New York]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Goshen, New York Context triple: [New York State Route 17, passesNear, Goshen, New York]
-
A.
Goshen, New York
chosen
Goshen, New York is a historic village in the Hudson Valley known for its role as the county seat and its longstanding equestrian and agricultural heritage.
-
B.
Goshen
Goshen was a short-lived Boer republic in southern Africa established by Voortrekker settlers during the 1880s.
-
C.
Goshen
Goshen is a small city in northern Indiana known for its manufacturing base, Mennonite and Amish heritage, and historic downtown.
-
D.
Goshen
Goshen is a small town in Utah County, Utah, situated in the southern part of Utah Valley.
-
E.
Goshen
Goshen is the fertile region in ancient Egypt where the Israelites settled during the time of Joseph, as recounted in the Book of Genesis.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de9083f9d081908fe5c99655c410b3 |
completed | April 14, 2026, 7:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd551eb09c8190a102ab452371e5b1 |
completed | May 8, 2026, 3:14 a.m. |
Created at: April 10, 2026, 1:17 a.m.