Triple
T35961220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aghdam region |
E1039998
|
entity |
| Predicate | formerFrontlineArea |
P190027
|
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: [Aghdam region, formerFrontlineArea, Nagorno-Karabakh conflict]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerFrontlineArea Context triple: [Aghdam region, formerFrontlineArea, Nagorno-Karabakh conflict]
-
A.
frontLineRegion
Indicates that a region is located at or constitutes the primary area of direct engagement or contact in a conflict, competition, or critical situation.
-
B.
frontlineAdvance
Indicates a movement of military or conflict front lines forward into previously uncontrolled or enemy-held territory.
-
C.
wasFrontlineAreaDuring
chosen
Indicates that a location served as a primary combat or conflict zone during a specified time period.
-
D.
frontLine
Indicates that an entity is positioned at or associated with the foremost or primary line of engagement, activity, or defense relative to others.
-
E.
frontLineFeature
Indicates that the subject is a prominent or leading characteristic that stands out at the forefront relative to others.
- 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_69f76e26b21081909fd9ffb3aff6c77a |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a007aa8d3a481908543f9b5d562a90c |
completed | May 10, 2026, 12:31 p.m. |
| PD | Predicate disambiguation | batch_6a007a44996481908688ccfdbc56511d |
completed | May 10, 2026, 12:29 p.m. |
Created at: May 3, 2026, 4:07 p.m.