Triple
T29547254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khojaly District |
E749662
|
entity |
| Predicate | longDisputed |
P158217
|
FINISHED |
| Object | Nagorno-Karabakh conflict |
—
|
NE NERFINISHED |
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: Nagorno-Karabakh conflict | Statement: [Khojaly District, longDisputed, Nagorno-Karabakh conflict]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: longDisputed Context triple: [Khojaly District, longDisputed, Nagorno-Karabakh conflict]
-
A.
laterDisputedBy
Indicates that a previously made claim, statement, or assertion is subsequently challenged, questioned, or contradicted by another party.
-
B.
significantDispute
Indicates a serious, often prolonged disagreement or conflict exists between the involved entities.
-
C.
disputeDuration
chosen
Indicates the length of time over which a dispute persists or remains unresolved between parties.
-
D.
disputed
Indicates that there is active disagreement or contestation over the validity, ownership, interpretation, or status of the relationship or claim between the entities.
-
E.
countIsDisputed
Indicates that the reported numerical value (such as a count, total, or tally) is contested or not agreed upon by relevant parties.
- 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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66cf471d88190af960f2c9959878e |
completed | May 2, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 5:08 p.m.