Triple
T36056724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Politics of Jersey |
E1042966
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | politics of a British Crown Dependency |
C33073
|
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: politics of a British Crown Dependency Context triple: [Politics of Jersey, instanceOf, politics of a British Crown Dependency]
-
A.
politics of a British Crown dependency
chosen
The politics of a British Crown dependency encompasses the unique constitutional arrangements, self-governing institutions, and relationships with the British Crown and UK government that shape its internal governance and external affairs.
-
B.
politics of an overseas territory
The politics of an overseas territory encompasses the institutions, power relations, and decision-making processes through which the territory is governed, both internally and in its dependent relationship with the metropolitan state.
-
C.
politics of England
Politics of England encompasses the structures, processes, parties, and power relations through which public decisions are made and governance is exercised within England’s constitutional and institutional framework.
-
D.
Crown dependency
A Crown dependency is a self-governing territory under the sovereignty of the British Crown that is not part of the United Kingdom but relies on it for defense and international representation.
-
E.
Alderney legislation
Alderney legislation comprises the body of laws, ordinances, and regulations enacted or applied by the States of Alderney to govern the island’s internal affairs and legal framework.
- 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_69f76e2f09448190b0486d5ecad5e243 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:08 p.m.