Triple
T1759385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Otto von Kotzebue |
E38620
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Imperial Russian 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 Russian Navy officer Context triple: [Otto von Kotzebue, instanceOf, Imperial Russian Navy officer]
-
A.
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.
-
B.
military officer
A military officer is a formally commissioned leader in the armed forces responsible for planning, directing, and managing operations, personnel, and resources to achieve strategic and tactical objectives.
-
C.
oblast of the Russian Empire
An oblast of the Russian Empire was an administrative-territorial unit, typically on the empire’s periphery, governed by appointed officials and possessing a lower status than a governorate (guberniya).
-
D.
naval rank
A naval rank is a formal title that defines an individual's level of authority, responsibility, and position within a navy's hierarchical command structure.
-
E.
Imperial Japanese Navy institution
An Imperial Japanese Navy institution is an organized body, such as a naval academy, staff college, research bureau, or administrative office, that supported the training, planning, governance, and operational effectiveness of the Imperial Japanese Navy.
- 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_69a8862d562481908d7025a1c1f67c0d |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:31 p.m.