Triple
T14694325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viktor Harder |
E345113
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Imperial German Navy 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: Imperial German Navy officer Context triple: [Viktor Harder, instanceOf, Imperial German Navy officer]
-
A.
Kriegsmarine admiral
A Kriegsmarine admiral is a high-ranking naval officer of Nazi Germany’s World War II navy, responsible for commanding major fleets, naval operations, and strategic maritime planning.
-
B.
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.
-
C.
Argentine naval officer
An Argentine naval officer is a commissioned member of Argentina’s navy responsible for leading personnel, operating and commanding naval vessels or units, and executing maritime defense, security, and strategic missions under national and international regulations.
-
D.
Austro-Hungarian military officer
An Austro-Hungarian military officer was a commissioned leader in the armed forces of the Austro-Hungarian Empire, responsible for commanding troops, implementing imperial military policy, and upholding the dual monarchy’s authority across its diverse territories.
-
E.
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.
- 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:28 a.m.