Triple
T18410546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Stephenson site |
E441745
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | War of 1812 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: War of 1812 historic site Context triple: [Fort Stephenson site, instanceOf, War of 1812 historic site]
-
A.
United States National Military Park
A United States National Military Park is a federally protected area that preserves and interprets significant military battlefields or related historic sites for public education, commemoration, and recreation.
-
B.
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.
-
C.
Frederick Douglass National Historic Site
Frederick Douglass National Historic Site is a preserved historic home and museum in Washington, D.C., dedicated to interpreting the life, legacy, and activism of abolitionist Frederick Douglass.
-
D.
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.
-
E.
Revolutionary War site
A Revolutionary War site is a historically significant location where events, battles, encampments, or strategic activities related to the American Revolutionary War took place and are preserved or interpreted today.
- 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_69d8b9eb8a508190a942fd75ebd8b1dc |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10:47 a.m.