Triple
T7979033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Sheriff of Devon |
E185518
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public office in England |
C122
|
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: public office in England Context triple: [High Sheriff of Devon, instanceOf, public office in England]
-
A.
Commonwealth of England office
A Commonwealth of England office is an administrative or governmental position or institution that operated under the republican regime of England (1649–1660), responsible for executing the functions of state in the absence of a monarchy.
-
B.
public office
chosen
A public office is an official position of authority and responsibility within a government or public institution, held to serve the interests and welfare of the public under established laws and regulations.
-
C.
private office
A private office is an enclosed workspace designated for an individual or small group, providing privacy, reduced noise, and a controlled environment for focused work and confidential activities.
-
D.
office within a government department
An office within a government department is an organizational unit responsible for carrying out specific administrative, regulatory, or programmatic functions under the department’s authority.
-
E.
United Kingdom government ministerial office
A United Kingdom government ministerial office is an official position within His Majesty’s Government held by a minister who is responsible for directing a specific department or policy area and accountable to Parliament for its administration and performance.
- 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_69ca829851908190b4e03829353ee7c3 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:14 p.m.