Triple
T9736635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sub-Lieutenant (Royal Naval Reserve) |
E236079
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military rank of the United Kingdom |
C7656
|
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: military rank of the United Kingdom Context triple: [Sub-Lieutenant (Royal Naval Reserve), instanceOf, military rank of the United Kingdom]
-
A.
army rank
An army rank is a formal level of authority and responsibility within a military hierarchy that defines a soldier’s position, duties, and chain-of-command relationships.
-
B.
British military office
A British military office is an administrative and command center within the United Kingdom’s armed forces where military personnel coordinate operations, manage logistics, and handle official defense-related documentation and communications.
-
C.
historical military rank
A historical military rank is a formally defined level of authority and responsibility within past armed forces, reflecting the hierarchical structure, duties, and social status of military personnel in a specific historical context.
-
D.
military rank structure
A military rank structure is a hierarchical system that organizes service members into levels of authority and responsibility, defining command relationships, roles, and progression within the armed forces.
-
E.
United Kingdom military position
chosen
A United Kingdom military position is a specific role or rank within the British Armed Forces, defined by its responsibilities, authority, and place in the military hierarchy.
- 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_69ca84d313e88190983ee6ffd0ef60d2 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:22 p.m.