Triple
T33332327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Getashen |
E853439
|
entity |
| Predicate | hasRoleInConflict |
P195828
|
FINISHED |
| Object | site of tensions during Nagorno-Karabakh conflict |
—
|
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: site of tensions during Nagorno-Karabakh conflict | Statement: [Getashen, hasRoleInConflict, site of tensions during Nagorno-Karabakh conflict]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoleInConflict Context triple: [Getashen, hasRoleInConflict, site of tensions during Nagorno-Karabakh conflict]
-
A.
hasConflictStatus
Indicates that there exists a state of conflict or dispute associated with the relationship between the involved entities.
-
B.
hasOngoingConflict
Indicates that there is a current, unresolved state of opposition, dispute, or hostilities between the related entities.
-
C.
hasNotableConflict
Indicates a significant, recognized dispute, clash, or opposition existing between the related entities.
-
D.
hasConflictCause
Indicates that one entity is the cause or source of a conflict involving another entity.
-
E.
hasConflictScale
Indicates the degree or intensity of conflict present in a given relationship, situation, or interaction.
- 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_69f34969614c81909cd99661b0902533 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fde9fc184c8190bebef35df0e76076 |
completed | May 8, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69fde6e5beb4819094945a695e961d88 |
completed | May 8, 2026, 1:36 p.m. |
| PDg | Predicate description generation | batch_69fde9fb68388190ada4a7018e2a2f76 |
completed | May 8, 2026, 1:49 p.m. |
Created at: May 1, 2026, 1:34 a.m.