Triple
T7800785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vice Lord Lieutenant of Lancashire |
E180424
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | deputy lieutenancy position |
C22580
|
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: deputy lieutenancy position Context triple: [Vice Lord Lieutenant of Lancashire, instanceOf, deputy lieutenancy position]
-
A.
deputy lieutenants
chosen
Deputy lieutenants are appointed representatives who assist a lord-lieutenant or equivalent senior official in carrying out ceremonial, civic, and administrative duties within a specific jurisdiction.
-
B.
Lord Lieutenant
A Lord Lieutenant is the British monarch’s personal representative in a county or area, responsible for arranging royal visits, presenting honors, and supporting civic, voluntary, and military activities.
-
C.
defense ministry deputy position
A defense ministry deputy position is a senior governmental role that assists the defense minister in formulating, coordinating, and overseeing national defense policies, military operations, and administrative functions.
-
D.
colonial-style administrative position
A colonial-style administrative position is a formal role within a governance system modeled on historical colonial administrations, typically involving hierarchical authority over territories, resources, and local populations on behalf of a distant central power.
-
E.
vice-regal representative
A vice-regal representative is an official who acts on behalf of a monarch or sovereign in a specific territory, performing constitutional, ceremonial, and administrative duties.
- 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_69ca827e50cc8190a92a733577184938 |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 4:33 p.m.