Triple
T27023049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karen Peace Council |
E680715
|
entity |
| Predicate | hasCooperatedWith |
P60681
|
FINISHED |
| Object | Government of Myanmar |
—
|
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: Government of Myanmar | Statement: [Karen Peace Council, hasCooperatedWith, Government of Myanmar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCooperatedWith Context triple: [Karen Peace Council, hasCooperatedWith, Government of Myanmar]
-
A.
frequentlyCollaboratedWith
Indicates that two entities have worked together on shared activities or projects on a recurring or regular basis.
-
B.
hasCollaboratedIn
chosen
Indicates that two or more entities have worked together on a shared project, task, or activity.
-
C.
partnerInActWith
Indicates that two or more entities jointly participate as partners in carrying out the same act or action.
-
D.
definesCooperationWith
Indicates that one entity formally specifies or establishes the terms, scope, or nature of cooperative interaction with another entity.
-
E.
hasSubsequentCollaboration
Indicates that one entity engages in a follow-up or later collaboration with another entity after an initial joint activity or partnership.
- 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_69eeeb5450988190bfc9a3c012ac463a |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69feaa483fcc81909d8a46b38a8717bf |
completed | May 9, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69fea8c9d45c81908ccc8619e5fefac1 |
completed | May 9, 2026, 3:23 a.m. |
Created at: April 27, 2026, 7:09 a.m.