Triple
T12389664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Douglas Cause |
E295957
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 18th-century court case |
C22140
|
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 court case Context triple: [Douglas Cause, instanceOf, 18th-century court case]
-
A.
colonial legal case
A colonial legal case is a formal dispute or prosecution adjudicated within a legal system established by a colonial power over a subject territory, reflecting the laws, institutions, and power dynamics of colonial rule.
-
B.
18th-century event
chosen
An 18th-century event is a historically significant occurrence between 1701 and 1800 that reflects the political, social, cultural, or technological developments of that period.
-
C.
19th-century controversy
A 19th-century controversy is a significant public dispute or prolonged debate during the 1800s, often involving social, political, scientific, or religious issues that shaped contemporary thought and policy.
-
D.
British court
A British court is a judicial body within the United Kingdom’s legal system that interprets and applies the law to resolve disputes, administer justice, and uphold legal rights and obligations.
-
E.
early 18th-century conflict
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.
- 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_69d6ad9e653c8190b1473c860ee53dae |
completed | April 8, 2026, 7:33 p.m. |
Created at: April 8, 2026, 9:54 p.m.