Triple
T35961225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aghdam region |
E1039998
|
entity |
| Predicate | sawMassDisplacementOf |
P184286
|
FINISHED |
| Object | Azerbaijani civilians |
—
|
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: Azerbaijani civilians | Statement: [Aghdam region, sawMassDisplacementOf, Azerbaijani civilians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sawMassDisplacementOf Context triple: [Aghdam region, sawMassDisplacementOf, Azerbaijani civilians]
-
A.
standardDisplacement
Indicates the typical or officially specified amount of displacement (such as volume, weight, or capacity) associated with an entity under standard conditions.
-
B.
displacementSubmerged
Indicates the amount of fluid displaced by an object when it is submerged.
-
C.
designedDisplacement
Indicates the intended or specified amount of displacement (such as volume or weight moved) that something is engineered or planned to produce or accommodate.
-
D.
massWithSailDeployed
Indicates the total mass of an object when its sail is fully deployed.
-
E.
notableDisplacement
Indicates a significant change in an entity’s usual position, location, or alignment relative to a reference point or state.
- 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_69f76e26b21081909fd9ffb3aff6c77a |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7acaec1508190a38f2ac9cc5383e7 |
completed | May 3, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69f7ac2210e481909279dade5328825c |
completed | May 3, 2026, 8:12 p.m. |
Created at: May 3, 2026, 4:07 p.m.