Triple
T8305230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Fire of New York (1776) |
E194447
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | disaster in New York City |
C223
|
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: disaster in New York City Context triple: [Great Fire of New York (1776), instanceOf, disaster in New York City]
-
A.
New York City community board
A New York City community board is a local advisory group of appointed residents that consults on land use, budget, and service delivery issues within a specific community district.
-
B.
location in Manhattan
A location in Manhattan represents a specific, identifiable place within the borough’s geographic boundaries, such as an address, landmark, intersection, or point of interest.
-
C.
disaster
chosen
A disaster is a sudden, disruptive event—natural or human-made—that causes significant harm to people, property, or the environment and overwhelms normal coping capacities.
-
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.
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.
- F. None of above.
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_69ca82e613e88190bf8139669bbd0d53 |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:54 p.m.