Triple
T26131770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry Robertson Bowers |
E659268
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Royal Indian Marine officer |
C192
|
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 Indian Marine officer Context triple: [Henry Robertson Bowers, instanceOf, Royal Indian Marine officer]
-
A.
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.
-
B.
Indian Navy sailor
An Indian Navy sailor is an enlisted maritime professional who operates, maintains, and supports naval ships, submarines, and aircraft to safeguard India’s maritime interests and national security.
-
C.
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.
-
D.
Indian Air Force officer
An Indian Air Force officer is a commissioned leader in India's aerial defense forces responsible for planning, directing, and executing air operations, managing personnel and resources, and upholding national security and military discipline.
-
E.
naval officer
chosen
A naval officer is a commissioned leader in a navy responsible for commanding personnel and vessels, making strategic and tactical decisions, and ensuring the effective operation and readiness of maritime forces.
- 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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
Created at: April 26, 2026, 8:15 p.m.