Triple
T30630989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 8888 Uprising |
E779711
|
entity |
| Predicate | perpetratorOfCrackdown |
P698
|
FINISHED |
| Object | Burmese armed forces |
—
|
NE NERFINISHED |
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: Burmese armed forces | Statement: [8888 Uprising, perpetratorOfCrackdown, Burmese armed forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perpetratorOfCrackdown Context triple: [8888 Uprising, perpetratorOfCrackdown, Burmese armed forces]
-
A.
perpetratorOfCrimeAgainst
Indicates that one entity is the person or group responsible for committing a crime against another entity.
-
B.
perpetratorProgram
Indicates that a program or software system is the agent responsible for carrying out a particular harmful, illegal, or otherwise wrongful action.
-
C.
perpetratedBy
chosen
Indicates that an action, event, or wrongdoing was carried out or caused by a particular agent or entity.
-
D.
perpetratedAttackOn
Indicates that one entity carried out, organized, or was responsible for an attack directed against another entity.
-
E.
perpetratorCommunity
Indicates that a community is responsible for committing or supporting the harmful act or offense in question.
- 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_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:28 p.m.