Triple
T19789581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kumyks |
E475372
|
entity |
| Predicate | sovietHistory |
P137336
|
FINISHED |
| Object | subject to collectivization |
—
|
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: subject to collectivization | Statement: [Kumyks, sovietHistory, subject to collectivization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sovietHistory Context triple: [Kumyks, sovietHistory, subject to collectivization]
-
A.
sovietPeriodName
Indicates that the object is the name used for the subject during the Soviet period.
-
B.
sharesSovietLegacyWith
Indicates that two entities have a common historical, political, or cultural background rooted in the former Soviet Union.
-
C.
roleInSovietUnion
Indicates that an entity held a specific position, function, or status within the governmental, political, or institutional structure of the Soviet Union.
-
D.
SovietFront
Indicates a military relationship where a unit, operation, or event is associated with or occurs on a Soviet military front (a major wartime operational formation).
-
E.
sovietStrength
Indicates the level or degree of strength, power, or capability associated with the Soviet side in a given context or interaction.
- 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_69d8e51b014081908b263e167370529a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6538ae5108190b80eb7de6f445f02 |
completed | April 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69e53053ed2881908400becdfada7fd3 |
completed | April 19, 2026, 7:43 p.m. |
| PDg | Predicate description generation | batch_69e532bcf41c8190b685b5adf46a60fc |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:49 p.m.