Triple
T2451783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coronation of Queen Anne |
E53720
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 18th-century event in England |
C7387
|
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: 18th-century event in England Context triple: [Coronation of Queen Anne, instanceOf, 18th-century event in England]
-
A.
18th-century art event
An 18th-century art event is a historically situated gathering, exhibition, performance, or public display centered on the creation, presentation, or discussion of visual or decorative arts produced during the 1700s.
-
B.
colonial-era event
A colonial-era event is a historically significant occurrence that took place during a period when one nation exercised political, economic, or cultural control over foreign territories and populations.
-
C.
early 18th-century conflict
chosen
An early 18th-century conflict is a historically situated armed struggle or war occurring roughly between 1700 and 1750, shaped by emerging nation-states, dynastic rivalries, and evolving military technologies and tactics.
-
D.
18th-century organization
An 18th-century organization is a formally or informally structured group of individuals operating during the 1700s to pursue political, economic, social, religious, or intellectual objectives within the historical context of early modern society.
-
E.
event in the Norman Conquest of England
An event in the Norman Conquest of England is a specific historical occurrence between 1066 and 1071 that contributed to William of Normandy’s seizure and consolidation of power over England.
- 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_69ab495d227c8190b26ae6548eeb1019 |
completed | March 6, 2026, 9:38 p.m. |
Created at: March 6, 2026, 9:43 p.m.