Triple
T32856959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copake Falls |
E840400
|
entity |
| Predicate | hasNearbyHistoricResource |
P72879
|
FINISHED |
| Object | former Copake Iron Works site |
—
|
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: former Copake Iron Works site | Statement: [Copake Falls, hasNearbyHistoricResource, former Copake Iron Works site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyHistoricResource Context triple: [Copake Falls, hasNearbyHistoricResource, former Copake Iron Works site]
-
A.
hasNearbyHistoricArea
chosen
Indicates that one entity is located close to another entity that is designated as a historic area.
-
B.
hasNearbyHistoricPeriod
Indicates that one historic period occurs close in time or space to another historic period.
-
C.
hasAdjacentHistoricSite
Indicates that one place is directly next to or very near another place that is recognized as a historic site.
-
D.
nearbyHistoricalServiceFor
Indicates that a historical service or facility is located close to a given reference entity or location.
-
E.
nearbyHistoricalFunction
Indicates that one entity is located close to another entity that has or had a historical role, use, or function.
- 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_69f349412c78819084459850e11d29f7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff63225b6481909217ad11b4f7d3ba |
completed | May 9, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ff60e0882c819085d097010db43ee0 |
completed | May 9, 2026, 4:29 p.m. |
Created at: May 1, 2026, 1:17 a.m.