Triple
T26026044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Chappaqua Historic District |
E647293
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic place in New York |
C50467
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: historic place in New York Context triple: [Old Chappaqua Historic District, instanceOf, historic place in New York]
-
A.
New York State Historic Site
A New York State Historic Site is a location officially designated and managed by New York State for its significant historical, cultural, or architectural importance.
-
B.
New York City cultural site
A New York City cultural site is a location within the city—such as a museum, theater, gallery, landmark, or performance space—dedicated to preserving, presenting, or fostering artistic, historical, or community-based cultural expression.
-
C.
landmark in New York City
A landmark in New York City is a notable, often historically or culturally significant site, building, or structure officially recognized for its importance to the city’s heritage and identity.
-
D.
New York City designated landmark
A New York City designated landmark is a building, site, object, or district officially recognized and protected by the New York City Landmarks Preservation Commission for its special historical, cultural, or architectural significance.
-
E.
municipality in New York
A municipality in New York is a legally incorporated local government entity—such as a city, town, or village—established under New York State law to provide public services and governance within a defined geographic area.
- F. None of above. chosen
Provenance (1 batch)
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_69e77e8b60e88190a3b26c4f0032a2c2 |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 22, 2026, 9:05 a.m.