Triple
T37103654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalmyk ASSR |
E918776
|
entity |
| Predicate | sovietRepublicLevel |
P187149
|
FINISHED |
| Object | second-level administrative division |
—
|
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: second-level administrative division | Statement: [Kalmyk ASSR, sovietRepublicLevel, second-level administrative division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sovietRepublicLevel Context triple: [Kalmyk ASSR, sovietRepublicLevel, second-level administrative division]
-
A.
sovietStrength
Indicates the level or degree of strength, power, or capability associated with the Soviet side in a given context or interaction.
-
B.
formerSovietRepublic
Indicates that an entity is a country or region that was once part of the Soviet Union but is now independent.
-
C.
SovietObjective
Indicates that the entity represents a goal, target, or strategic aim pursued by the Soviet Union.
-
D.
successorStateOnSovietSide
Indicates that one state is recognized as the political or legal successor to a former state that was part of the Soviet sphere or structure.
-
E.
SovietForceType
Indicates that the entity is classified as a type or category of Soviet military force.
- 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_69f76e9b99c8819096164b21ff5bd996 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb344ba5408190a6fe8face293d88b |
completed | May 6, 2026, 12:30 p.m. |
Created at: May 3, 2026, 4:14 p.m.