Triple
T28912161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Master Sun |
E733256
|
entity |
| Predicate | conflictRelation |
P168743
|
FINISHED |
| Object | core participant in main conflicts |
—
|
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: core participant in main conflicts | Statement: [Master Sun, conflictRelation, core participant in main conflicts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictRelation Context triple: [Master Sun, conflictRelation, core participant in main conflicts]
-
A.
conflictRelatedStatus
Indicates a status or condition that is directly associated with, affected by, or resulting from a conflict.
-
B.
relateradKonflikt
Indicates that there is a related or associated conflict between the entities involved.
-
C.
conflictCountry
Indicates that there is an armed conflict or war involving the referenced country as a participant.
-
D.
partnerInConflictWith
Indicates that two entities are engaged as opposing partners or sides within the same conflict or dispute.
-
E.
conflictOrCooperationWith
Indicates the presence, nature, or degree of either conflict or cooperation between two entities.
- 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_69f05b096d208190958a57d2e4b5a93a |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f67805551c81909e016ae9e3031076 |
completed | May 2, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676f73c3481909f01fa69851b7298 |
completed | May 2, 2026, 10:13 p.m. |
Created at: April 28, 2026, 8:12 a.m.