Triple
T316377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yuri Gagarin |
E7715
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet military officer |
C449
|
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: Soviet military officer Context triple: [Yuri Gagarin, instanceOf, Soviet military officer]
-
A.
military officer
chosen
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.
-
B.
general of the army
A general of the army is the highest-ranking military officer responsible for overseeing large-scale strategic planning, command, and coordination of an entire nation's land forces.
-
C.
naval officer
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.
-
D.
intelligence officer
An intelligence officer is a professional responsible for collecting, analyzing, and disseminating sensitive information to support national security, military operations, or organizational decision-making.
-
E.
World War II veteran
A World War II veteran is an individual who served in the armed forces of any nation during the global conflict of 1939–1945, participating in military operations or support roles related to the war.
- 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.