Triple
T28018351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mariot Arbuthnot |
E707614
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British Royal Navy officer |
C53674
|
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: British Royal Navy officer Context triple: [Mariot Arbuthnot, instanceOf, British Royal Navy officer]
-
A.
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.
-
B.
Royal Indian Navy sailor
A Royal Indian Navy sailor is an enlisted maritime servicemember who operated, maintained, and supported naval vessels and missions under British colonial rule in the Indian subcontinent.
-
C.
Royal Navy organization
A Royal Navy organization is a structured entity within the United Kingdom’s naval service responsible for planning, directing, and supporting maritime operations, personnel, and resources to achieve national defense and security objectives.
-
D.
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.
-
E.
Irish naval officer
An Irish naval officer is a commissioned member of Ireland’s naval forces responsible for leading sailors, managing maritime operations, and safeguarding the nation’s territorial waters and maritime interests.
- F. None of above. chosen
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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
Created at: April 27, 2026, 8:08 p.m.