Triple
T7959547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orange River region |
E184825
|
entity |
| Predicate | conflictsType |
P1397
|
FINISHED |
| Object | land 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: land conflicts | Statement: [Orange River region, conflictsType, land conflicts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictsType Context triple: [Orange River region, conflictsType, land conflicts]
-
A.
conflictType
chosen
Indicates the specific kind or category of conflict that characterizes the relationship or interaction between entities.
-
B.
conflictWith
Indicates that two entities are in opposition or disagreement, such that their goals, actions, or states are incompatible or interfere with each other.
-
C.
conflictedBetween
Indicates being torn or uncertain between two or more options, positions, or commitments.
-
D.
usedInConflictType
Indicates that something (such as a resource, method, or capability) is employed or applied within a specific type or category of conflict.
-
E.
typicalConflict
Indicates that there is a commonly occurring or characteristic conflict or opposition between the related entities.
- 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_69ca8293a2388190aace944d7ed9c0c0 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b80050c81909b2db95ade495052 |
completed | March 31, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69cb0473d7dc8190a25d0cf460b9fcbe |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:11 p.m.