Triple
T29574512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Fort St. Jean (1775) |
E753405
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in 1775 |
C14349
|
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: event in 1775 Context triple: [Siege of Fort St. Jean (1775), instanceOf, event in 1775]
-
A.
Revolutionary War event
chosen
A Revolutionary War event is a significant occurrence—such as a battle, political decision, treaty, or social upheaval—that directly influenced the course, conduct, or outcome of the American Revolutionary War.
-
B.
event in 1781
An event in 1781 is any historically significant occurrence—political, social, cultural, scientific, or military—that took place during the calendar year 1781.
-
C.
event in King Philip's War
An event in King Philip's War is a specific historical incident, battle, negotiation, or turning point that occurred during the 1675–1678 conflict between Native American tribes and English colonists in New England.
-
D.
event in King Philip's War
An event in King Philip's War is a specific historical incident, battle, negotiation, or turning point that occurred between 1675 and 1678 during the conflict between Native American tribes and English colonists in New England.
-
E.
Revolutionary War institution
A Revolutionary War institution is an organized body, such as a military, governmental, or civic entity, established or transformed during the American Revolution to support, administer, or legitimize the war effort and emerging nation.
- 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_69f0ef7fcb4881908a933110adb9bda1 |
completed | April 28, 2026, 5:33 p.m. |
Created at: April 28, 2026, 6:01 p.m.