Triple
T6802936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shinto Directive |
E156230
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Allied directive |
C9943
|
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: Allied directive Context triple: [Shinto Directive, instanceOf, Allied directive]
-
A.
Allied military authority
chosen
An Allied military authority is a governing body established by cooperating allied nations' armed forces to administer, control, and coordinate military and sometimes civil affairs in occupied or liberated territories during and immediately after conflict.
-
B.
joint command
A joint command is a unified military authority structure that coordinates and directs operations involving multiple service branches or allied forces to achieve common strategic objectives.
-
C.
war crime directive
A war crime directive is an explicit order or policy issued by an authority that instructs or authorizes the commission of actions that violate international humanitarian law during armed conflict.
-
D.
bilateral command
A bilateral command is an instruction or directive that involves or requires coordinated action, agreement, or communication between two distinct parties or sides.
-
E.
missionary directive
A missionary directive is an authoritative instruction or set of guidelines that defines the goals, methods, and ethical boundaries for individuals or groups engaged in religious outreach or proselytizing activities.
- 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_69c68826e6a48190a3d220b541e639de |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:16 p.m.