Triple
T20310956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hatfield–McCoy historic sites |
E510239
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | American historic site |
C11600
|
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: American historic site Context triple: [Hatfield–McCoy historic sites, instanceOf, American historic site]
-
A.
Historic site
chosen
A historic site is a location of significant past events, structures, or cultural heritage that is preserved and recognized for its historical importance.
-
B.
United States National Historical Park
A United States National Historical Park is a protected area designated by the federal government to preserve and interpret places of national historical significance, often encompassing multiple sites or a large landscape associated with important events, people, or themes in American history.
-
C.
American history center
An American history center is an educational institution or facility dedicated to collecting, preserving, interpreting, and presenting artifacts, documents, and narratives related to the historical development of the United States.
-
D.
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.
-
E.
national heritage site
A national heritage site is a location, structure, or landscape officially designated by a country as having significant historical, cultural, architectural, or natural value warranting legal protection and 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_69e0b4c7491c8190961113c4283b10b0 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 11:19 a.m.