Triple
T24537993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Star Fort |
E607004
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in 1781 |
C48856
|
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 1781 Context triple: [Siege of Star Fort, instanceOf, event in 1781]
-
A.
event in the War of the Quadruple Alliance
An event in the War of the Quadruple Alliance is a specific historical occurrence—such as a battle, treaty, diplomatic action, or political development—that took place between 1718 and 1720 and directly influenced the course or outcome of that conflict.
-
B.
event in the War of 1812
An "event in the War of 1812" is a specific historical occurrence—such as a battle, treaty, political decision, or military campaign—that took place between 1812 and 1815 and directly relates to the conflict between the United States, the United Kingdom, and their respective allies.
-
C.
event in the Seven Years' War
An event in the Seven Years' War is a specific historical occurrence—such as a battle, treaty, campaign, or political decision—that took place between 1756 and 1763 and significantly influenced the course or outcome of the global conflict.
-
D.
Revolutionary War event
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.
-
E.
event in 1811
An event in 1811 is any significant occurrence, action, or development that took place during the calendar year 1811.
- 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_69e2c4c90c848190b23c4303620dcaaf |
completed | April 17, 2026, 11:39 p.m. |
Created at: April 18, 2026, 2:26 a.m.