Triple
T4298207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ural Cossack forces |
E99767
|
entity |
| Predicate | statusAfterCivilWar |
P4701
|
FINISHED |
| Object | suppressed |
—
|
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: suppressed | Statement: [Ural Cossack forces, statusAfterCivilWar, suppressed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfterCivilWar Context triple: [Ural Cossack forces, statusAfterCivilWar, suppressed]
-
A.
functionAfterCivilWar
Indicates that one entity serves or operates in a particular function, role, or capacity following the end of a civil war.
-
B.
statusAfter1865
Indicates the condition or state of an entity as it existed after the year 1865.
-
C.
civilWarPeriod
Indicates a time span during which a civil war is occurring or in effect.
-
D.
legalStatusAfterWar
chosen
Indicates the legal condition or classification assigned to an entity as a consequence of, or following the conclusion of, a war or armed conflict.
-
E.
preCivilWarOccupation
Indicates the occupation or role a person held before the outbreak of the Civil War.
- 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_69b3455175088190aa79c6e03b86647e |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3509bff808190a86fade7ccfc3611 |
completed | March 12, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69b347fe55a88190b77bab0c0f38e1aa |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:08 p.m.