Triple
T37509308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High King of the Alliance |
E932176
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional military office |
C1854
|
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: fictional military office Context triple: [High King of the Alliance, instanceOf, fictional military office]
-
A.
military office
chosen
A military office is an administrative workspace within an armed forces organization where personnel manage planning, logistics, communication, and documentation to support military operations.
-
B.
fictional judicial office
A fictional judicial office is an invented role or institution within an imagined legal system, endowed with specific authorities, procedures, and symbolic functions that shape how justice operates in that fictional world.
-
C.
military rank-equivalent office
A military rank-equivalent office is a formal position within a non-military organization that is structured, titled, and empowered to correspond directly to a specific military rank for purposes such as protocol, authority, or interoperability.
-
D.
fictional government ministry
A fictional government ministry is an imagined official department within a government, created in stories or worldbuilding to oversee specific policy areas, functions, or societal needs.
-
E.
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.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.