Triple
T24574544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royalist campaign in Cornwall |
E608067
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Royalist military operation |
C41986
|
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: Royalist military operation Context triple: [Royalist campaign in Cornwall, instanceOf, Royalist military operation]
-
A.
Royalist campaign
chosen
A Royalist campaign is an organized political or military effort aimed at supporting, restoring, or strengthening a monarchy and the authority of a reigning or rightful royal family.
-
B.
Portuguese military campaign
A Portuguese military campaign is a coordinated series of armed operations conducted by Portugal’s military forces to achieve specific strategic, political, or territorial objectives, often within a defined geographic area and time period.
-
C.
Royalist general
A Royalist general is a high-ranking military commander who leads armed forces in support of a monarchy, defending the authority and interests of the reigning royal family or crown.
-
D.
British colonial military operation
A British colonial military operation is a coordinated campaign conducted by British armed forces to establish, maintain, or expand control over territories within the British Empire, often involving combat, occupation, and enforcement of imperial policies.
-
E.
royalist resistance group
A royalist resistance group is an organized, often clandestine movement that actively opposes existing authorities or occupying powers in order to restore, preserve, or expand the power of a monarchy.
- 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_69e2c4cdab6c8190aae6e5d3de55c95e |
completed | April 17, 2026, 11:39 p.m. |
Created at: April 18, 2026, 2:29 a.m.