Triple
T29917605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trisakti shootings |
E759827
|
entity |
| Predicate | demandedOutcome |
P59870
|
FINISHED |
| Object | resignation of Suharto |
—
|
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: resignation of Suharto | Statement: [Trisakti shootings, demandedOutcome, resignation of Suharto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demandedOutcome Context triple: [Trisakti shootings, demandedOutcome, resignation of Suharto]
-
A.
demanded
Indicates that one entity forcefully or insistently requested something from another entity.
-
B.
outcomeOf
chosen
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
C.
demandedDuring
Indicates that one entity formally requested or required something from another entity within a specific time period or event.
-
D.
supportedOutcomeOf
Indicates that one entity serves as evidence, backing, or justification for the outcome or result represented by another entity.
-
E.
outcomeType
Indicates the specific category or nature of the result produced by an event, process, or action.
- 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_69f2246189fc8190996b63ee1f9a2374 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f677907930819081cd718537fdaf4a |
completed | May 2, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:13 p.m.