Triple
T28684116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Navy Court of Inquiry on Pearl Harbor |
E726084
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military investigative body |
C298
|
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 investigative body Context triple: [Navy Court of Inquiry on Pearl Harbor, instanceOf, military investigative body]
-
A.
military organization
chosen
A military organization is a structured group of armed forces personnel and resources, organized under a defined hierarchy and command system, to plan, coordinate, and conduct defense and combat operations in support of a state’s strategic objectives.
-
B.
military decision-making body
A military decision-making body is an organized group of authorized personnel responsible for analyzing strategic and tactical information, evaluating options, and issuing binding directives that guide military operations and policy.
-
C.
law enforcement body
A law enforcement body is an organized governmental agency responsible for maintaining public order, preventing and investigating crime, and enforcing laws within a defined jurisdiction.
-
D.
paramilitary organization
A paramilitary organization is a structured group that operates with military-style training, hierarchy, and tactics but is not formally part of a recognized state's official armed forces.
-
E.
military political organ
A military political organ is an institutional body within the armed forces responsible for overseeing political education, ideological control, and party or state loyalty among military personnel.
- 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_69f01d867608819086bc3e6b4f9de866 |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 28, 2026, 5:11 a.m.