Triple
T36022952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mar Peerage Case |
E1042039
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Scottish peerage dispute |
C10904
|
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: Scottish peerage dispute Context triple: [Mar Peerage Case, instanceOf, Scottish peerage dispute]
-
A.
Privy Council case
A Privy Council case is a legal dispute heard and decided by the Judicial Committee of the Privy Council, typically serving as the highest court of appeal for certain Commonwealth countries and UK overseas territories.
-
B.
Scottish civil conflict
Scottish civil conflict refers to internal political, religious, and military struggles within Scotland, often involving rival noble factions, competing claims to the throne, and clashes over governance and national identity.
-
C.
British legal scandal
A British legal scandal is a high-profile controversy arising from alleged misconduct, corruption, or serious procedural failures within the United Kingdom’s legal or judicial system that undermines public trust in the rule of law.
-
D.
Jacobite claim
The Jacobite claim is the hereditary assertion by the descendants of the deposed Stuart dynasty to the thrones of England, Scotland, and Ireland, maintained in opposition to the post-1688 constitutional settlement.
-
E.
Scottish legal case
chosen
A Scottish legal case is a formal dispute brought before a Scottish court or tribunal to interpret and apply Scots law to specific facts and determine the rights and obligations of the parties involved.
- 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_69f76e2c568881909e1e21f85252b0f0 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.