Triple
T30629702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | judicial branch of Myanmar |
E779680
|
entity |
| Predicate | nominalIndependence |
P8371
|
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, nominalIndependence, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nominalIndependence Context triple: [judicial branch of Myanmar, nominalIndependence, yes]
-
A.
independenceFrom
Indicates that one entity is not controlled, governed, or significantly influenced by another entity.
-
B.
isIndependent
chosen
Indicates that an entity exists, functions, or operates without being controlled, influenced, or determined by another entity.
-
C.
typeOfIndependence
Indicates the specific nature or category of independence that applies to an entity or relationship.
-
D.
originallyIndependentOf
Indicates that one entity was initially separate from, and not derived from or influenced by, another entity at the outset.
-
E.
lacksIndependenceFrom
Indicates that one entity is not autonomous from another and is dependent on it for control, influence, or decision-making.
- F. None of above.
Provenance (3 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_69f68a1c41ec81909d892e7f364f1c5b |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:28 p.m.