Triple
T29737347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Ligonier |
E752500
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | French and Indian War site |
C56146
|
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: French and Indian War site Context triple: [Fort Ligonier, instanceOf, French and Indian War 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.
King Philip’s War site
A King Philip’s War site is a historically significant location directly associated with the events, battles, encampments, or aftermath of the 1675–1678 conflict between New England colonists and Indigenous peoples.
-
C.
American Revolutionary War site
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.
-
D.
Wampanoag cultural site
A Wampanoag cultural site is a place of historical, spiritual, or communal significance to the Wampanoag people, where traditional practices, stories, and connections to the land are preserved and honored.
-
E.
Second Seminole War site
A Second Seminole War site is a historically significant location associated with battles, encampments, negotiations, or other key events that occurred during the Second Seminole War (1835–1842) in Florida.
- F. None of above. chosen
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_69f0d62a36a88190bf860f00da433ff8 |
completed | April 28, 2026, 3:45 p.m. |
Created at: April 28, 2026, 7:46 p.m.