Triple
T9785734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karen Americans |
E237486
|
entity |
| Predicate | originatingConflict |
P90640
|
FINISHED |
| Object | Myanmar civil war |
—
|
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: Myanmar civil war | Statement: [Karen Americans, originatingConflict, Myanmar civil war]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originatingConflict Context triple: [Karen Americans, originatingConflict, Myanmar civil war]
-
A.
conflictIn
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
-
B.
originatingDispute
Indicates that one entity is the source, cause, or initial context of a particular dispute involving another entity.
-
C.
facedConflictOver
Indicates that two or more entities experienced opposition, dispute, or tension concerning a particular issue, resource, or situation.
-
D.
conflictIntroduced
Indicates that a conflict has been newly created or brought into existence between the related entities.
-
E.
hasCauseOfConflict
Indicates a relationship where one entity is the source or reason for a conflict involving another entity.
- F. None of above. chosen
Provenance (4 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_69ca84da927881909bda80caecad6010 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda2107f688190b2cab1509c508319 |
completed | April 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69cd03d77c6c81909b675955bf113320 |
completed | April 1, 2026, 11:39 a.m. |
| PDg | Predicate description generation | batch_69cd06aa8bc88190904be19c8953def8 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:27 p.m.