Triple
T22273211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoskins House |
E550532
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic building in the United States |
C5702
|
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 building in the United States Context triple: [Hoskins House, instanceOf, historic building in the United States]
-
A.
historic federal building
A historic federal building is a government-owned structure of significant age and architectural, cultural, or political importance that has played a notable role in the nation’s public affairs.
-
B.
Historic site
A historic site is a location of significant past events, structures, or cultural heritage that is preserved and recognized for its historical importance.
-
C.
Historic house
chosen
A historic house is a residential building recognized for its significant architectural, cultural, or historical value, often preserved or restored to reflect the period in which it was built.
-
D.
revitalized historic building
A revitalized historic building is a preserved architectural structure that has been thoughtfully restored and modernized to serve contemporary functions while maintaining its original character and cultural significance.
-
E.
structure on the National Register of Historic Places
A structure on the National Register of Historic Places is a building or constructed work officially recognized by the United States federal government as significant in American history, architecture, archaeology, engineering, or culture and deemed worthy of preservation.
- 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_69e11e43d8208190aff4f9cf7f2c2a8a |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:40 p.m.