Triple
T8622617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Circassian genocide |
E204203
|
entity |
| Predicate | peakEvent |
P84490
|
FINISHED |
| Object | Sochi area expulsions in 1864 |
—
|
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: Sochi area expulsions in 1864 | Statement: [Circassian genocide, peakEvent, Sochi area expulsions in 1864]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakEvent Context triple: [Circassian genocide, peakEvent, Sochi area expulsions in 1864]
-
A.
peakType
Indicates the specific classification or category of a peak based on its form, prominence, or other defining characteristics.
-
B.
peakFunction
Indicates that a function reaches a maximum (peak) value at a specific point or over a given interval.
-
C.
peakUse
Indicates the time, condition, or context in which something reaches its maximum level of use or intensity.
-
D.
peakStatus
Indicates the condition or phase of something at its highest or most intense point in its progression or lifecycle.
-
E.
impactEvent
Indicates that one entity physically strikes or collides with another, producing a resulting effect or change.
- 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_69ca834a4ea0819094970dceb9e389f3 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5730309081909a9a0256c9bf5f8f |
completed | March 31, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69cc455906f8819082edd79cb4a1cf28 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc572d99bc819097f36b140c2ee1ce |
completed | March 31, 2026, 11:22 p.m. |
Created at: March 30, 2026, 6:26 p.m.