Triple
T37219417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Washington’s Headquarters |
E922834
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Revolutionary War historic site |
C3992
|
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: Revolutionary War historic site Context triple: [George Washington’s Headquarters, instanceOf, Revolutionary War historic site]
-
A.
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.
-
B.
American Revolutionary War site
chosen
An American Revolutionary War site is a historically significant location where events related to the American struggle for independence—such as battles, encampments, political actions, or key decisions—took place and are preserved or commemorated today.
-
C.
War of 1812 site
A War of 1812 site is a historically significant location directly associated with military, political, or civilian events of the War of 1812, such as battlefields, forts, encampments, or related structures and landscapes.
-
D.
French and Indian War site
A French and Indian War site is a location significantly associated with military, political, or cultural events of the French and Indian War (1754–1763), such as battlefields, forts, encampments, or related historic landscapes.
-
E.
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.
- 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_69f76ea6f5288190b8d9988f613811c0 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:15 p.m.