Triple
T28850042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Navy Director of Naval Construction |
E728566
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | senior civil service post |
C42095
|
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: senior civil service post Context triple: [Royal Navy Director of Naval Construction, instanceOf, senior civil service post]
-
A.
senior civil servant role
chosen
A senior civil servant role is a high-level government position responsible for providing strategic leadership, policy advice, and oversight of public administration to ensure effective implementation of governmental objectives.
-
B.
cabinet-level government post
A cabinet-level government post is a senior executive position, typically heading a major department or ministry, that advises the head of government and helps formulate and implement national policy.
-
C.
civil service cadre
A civil service cadre is a structured group of professional government officials organized by rank, function, and career path to implement public policies and administer state affairs.
-
D.
senior United Nations position
A senior United Nations position is a high-level leadership role responsible for shaping and implementing UN policies, strategies, and operations across member states and agencies.
-
E.
senior clerical rank
A senior clerical rank is a high-level position within a religious or administrative hierarchy, typically involving significant authority, oversight responsibilities, and decision-making power over lower-ranking clerical roles.
- 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_69f0319f4e5481909e4c439dbe8be940 |
completed | April 28, 2026, 4:03 a.m. |
Created at: April 28, 2026, 6:43 a.m.