Triple
T1364540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Military Collegium of the Supreme Court of the USSR |
E29173
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military court |
C438
|
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 court Context triple: [Military Collegium of the Supreme Court of the USSR, instanceOf, military court]
-
A.
military tribunal
chosen
A military tribunal is a specialized court convened by the armed forces to try members of the military or, in some cases, civilians, for violations of military law or the laws of war.
-
B.
military justice code
A military justice code is a formal set of laws and regulations that governs the conduct, discipline, and legal procedures applicable to members of the armed forces.
-
C.
military legal code
A military legal code is a formal system of laws and regulations that governs the conduct, discipline, rights, and obligations of members of the armed forces.
-
D.
special court
A special court is a judicial body established to handle specific types of cases or issues outside the jurisdiction or procedures of ordinary courts, often with specialized rules, judges, or limited subject matter.
-
E.
military organization
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.
- 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_69a498d77abc8190913bf57e5f51d2c4 |
completed | March 1, 2026, 7:51 p.m. |
Created at: March 1, 2026, 7:57 p.m.