Triple
T35961219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aghdam region |
E1039998
|
entity |
| Predicate | returnedUnderControlOf |
P110013
|
FINISHED |
| Object | Azerbaijan in 2020 ceasefire |
—
|
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: Azerbaijan in 2020 ceasefire | Statement: [Aghdam region, returnedUnderControlOf, Azerbaijan in 2020 ceasefire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnedUnderControlOf Context triple: [Aghdam region, returnedUnderControlOf, Azerbaijan in 2020 ceasefire]
-
A.
isUnderControlOf
Indicates that one entity is subject to the authority, direction, or governance of another entity.
-
B.
endedControlOf
chosen
Indicates that one entity has ceased to exercise authority, influence, or governance over another entity or domain.
-
C.
returnedToUSControl
Indicates that control or authority over an entity has been transferred back to the United States.
-
D.
isControlledUnder
Indicates that one entity is subject to regulatory, legal, or authoritative control exercised by another entity or governing framework.
-
E.
operatesUnderControlOf
Indicates that one entity functions or carries out its activities subject to the authority, direction, or governance of another entity.
- 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_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 3, 2026, 4:07 p.m.