Triple
T28850043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Navy Director of Naval Construction |
E728566
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Royal Navy shore appointment |
C6127
|
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: Royal Navy shore appointment Context triple: [Royal Navy Director of Naval Construction, instanceOf, Royal Navy shore appointment]
-
A.
position in the Royal Navy administration
chosen
A position in the Royal Navy administration is an official role responsible for managing the organizational, logistical, financial, or strategic affairs that support the operation and governance of the Royal Navy.
-
B.
Royal Navy command position
A Royal Navy command position is an official role within the naval hierarchy responsible for directing ships, fleets, or shore establishments and overseeing personnel, operations, and strategic decision-making.
-
C.
Royal Navy station
A Royal Navy station is a geographically defined area or shore establishment from which Royal Navy forces are administered, supported, and directed for operations within a particular region.
-
D.
British Royal Navy officer
A British Royal Navy officer is a commissioned leader responsible for commanding ships, submarines, aircraft, or naval units, overseeing operations, personnel, and strategy in service of the United Kingdom’s maritime defense and interests.
-
E.
British auxiliary officer
A British auxiliary officer is a part-time or non-regular commissioned or non-commissioned member of the British armed forces who supports regular units in military, security, or administrative roles, often during emergencies or wartime.
- 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.