Triple
T29034852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jabrayil |
E737829
|
entity |
| Predicate | preWarPopulationTrend |
P165949
|
FINISHED |
| Object | depopulated after 1990s conflict |
—
|
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: depopulated after 1990s conflict | Statement: [Jabrayil, preWarPopulationTrend, depopulated after 1990s conflict]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preWarPopulationTrend Context triple: [Jabrayil, preWarPopulationTrend, depopulated after 1990s conflict]
-
A.
preWorldWarIIPopulationEstimate
Indicates an estimated value for an entity’s population during the period before the start of World War II.
-
B.
preWarEthnicComposition
Indicates the ethnic makeup or distribution of ethnic groups in a place or population before a specific war or armed conflict.
-
C.
preWarCountry
Indicates that a country existed or held a particular status prior to a specified war or major armed conflict.
-
D.
preWarOccupation
Indicates the occupation or role a person held before a specific war or armed conflict.
-
E.
preWarCapacity
Indicates the capacity or level something had before a war or major conflict occurred.
- 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6603be0cc8190ba34acec15092a98 |
completed | May 2, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65ad638ac8190a17bb987fce53279 |
completed | May 2, 2026, 8:13 p.m. |
Created at: April 28, 2026, 9:57 a.m.