Triple
T13145749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enga people |
E312329
|
entity |
| Predicate | traditionalConflictResolution |
P21013
|
FINISHED |
| Object | compensation payments |
—
|
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: compensation payments | Statement: [Enga people, traditionalConflictResolution, compensation payments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalConflictResolution Context triple: [Enga people, traditionalConflictResolution, compensation payments]
-
A.
conflictManagementMechanism
chosen
Indicates a relationship where a method, process, or system is used to prevent, manage, or resolve conflicts between parties or interests.
-
B.
conflictResolvedBy
Indicates that a conflict or dispute is settled or addressed through the actions, decisions, or intervention of a specified entity or process.
-
C.
typicalConflict
Indicates that there is a commonly occurring or characteristic conflict or opposition between the related entities.
-
D.
endedConflict
Indicates that a previously ongoing conflict between entities has been brought to an end.
-
E.
addressedConflictWith
Indicates that one entity has taken action to confront, manage, or resolve a conflict involving another entity.
- 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_69d806aabde48190899e13e41659cae5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bbd1d088190b7c69f37fc6eeb64 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:10 p.m.