Triple
T30629714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | judicial branch of Myanmar |
E779680
|
entity |
| Predicate | hasMilitaryJusticeSystem |
P181071
|
FINISHED |
| Object | yes |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: yes | Statement: [judicial branch of Myanmar, hasMilitaryJusticeSystem, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMilitaryJusticeSystem Context triple: [judicial branch of Myanmar, hasMilitaryJusticeSystem, yes]
-
A.
privateArmyJurisdiction
Indicates that a private army has authority, control, or operational responsibility within a particular area or over certain matters.
-
B.
courtMartialed
Indicates that a person has been subjected to a formal military trial for alleged violations of military law.
-
C.
hasExtendedLawSystem
Indicates that an entity possesses a comprehensive, detailed, and well-developed system of laws or legal regulations.
-
D.
deathPenaltyJurisdiction
Indicates that a given jurisdiction legally authorizes, applies, or recognizes the death penalty as a form of criminal punishment.
-
E.
legalSystemImposed
Indicates that one authority or group has established and enforced a particular legal system upon another population or territory.
- F. None of above. chosen
Provenance (4 batches)
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_69f224a431548190a44ad9d088dbf91f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
| PDg | Predicate description generation | batch_69f760a2a90c8190b8fbc55412ab752b |
completed | May 3, 2026, 2:50 p.m. |
Created at: April 29, 2026, 8:28 p.m.