Triple
T23983146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golkar Party |
E604558
|
entity |
| Predicate | hasBeenInGovernmentCoalition |
P100331
|
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: [Golkar Party, hasBeenInGovernmentCoalition, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeenInGovernmentCoalition Context triple: [Golkar Party, hasBeenInGovernmentCoalition, yes]
-
A.
governsInCoalition
Indicates that an entity exercises governing authority jointly with one or more partners as part of a political coalition.
-
B.
memberOfPoliticalCoalition
Indicates that an entity belongs to or participates as a constituent member in a specific political coalition.
-
C.
previousCoalitionMemberOf
chosen
Indicates that an entity was formerly a member of a particular coalition but is no longer part of it.
-
D.
servedInGovernmentWith
Indicates that two individuals held positions in the same government or administration during an overlapping period of time.
-
E.
resultedInCoalitionGovernment
Indicates that the event or outcome led to the formation of a coalition government between multiple political parties.
- 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_69e29543f40c819087700b7a272afb60 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d2bf02fc8190bebd59f149e0bbfc |
completed | April 29, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:30 p.m.