Triple
T33487067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armenia–Georgia border |
E857640
|
entity |
| Predicate | relatedConflictStatus |
P47615
|
FINISHED |
| Object | generally peaceful |
—
|
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: generally peaceful | Statement: [Armenia–Georgia border, relatedConflictStatus, generally peaceful]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedConflictStatus Context triple: [Armenia–Georgia border, relatedConflictStatus, generally peaceful]
-
A.
conflictRelatedStatus
chosen
Indicates a status or condition that is directly associated with, affected by, or resulting from a conflict.
-
B.
hasConflictStatus
Indicates that there exists a state of conflict or dispute associated with the relationship between the involved entities.
-
C.
relatedConflictRisk
Indicates a relationship where one entity is associated with, contributes to, or is affected by the risk of conflict involving another entity.
-
D.
statusDuringConflict
Indicates the role, condition, or standing an entity held throughout a specified conflict or period of hostilities.
-
E.
endedConflict
Indicates that a previously ongoing conflict between entities has been brought to an end.
- 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_69f3497547608190a1a0f2365fb713ee |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:38 a.m.