Triple
T287614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1936 Constitution of the Soviet Union |
E5917
|
entity |
| Predicate | limitedByPracticeOf |
P99
|
FINISHED |
| Object | one-party rule |
—
|
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: one-party rule | Statement: [1936 Constitution of the Soviet Union, limitedByPracticeOf, one-party rule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: limitedByPracticeOf Context triple: [1936 Constitution of the Soviet Union, limitedByPracticeOf, one-party rule]
-
A.
associatedWithPractice
Indicates a relationship in which an entity is connected or linked to a particular practice, activity, or customary way of doing something.
-
B.
practicedLawIn
Indicates that a person engaged in the professional practice of law within a specified jurisdiction or location.
-
C.
hasLimitation
chosen
Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
-
D.
eligibleUses
Indicates the types of actions, purposes, or contexts in which something is permitted or qualified to be used.
-
E.
scopeOfUse
Indicates the range, context, or conditions under which something is intended, allowed, or applicable to be used.
- 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_69a25946a7ac8190a78871c210213272 |
completed | Feb. 28, 2026, 2:56 a.m. |
| NER | Named-entity recognition | batch_69a25e2ddaa88190b08c40b5823f30a0 |
completed | Feb. 28, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69a25b7c1448819082064f474633acd5 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 3:02 a.m.