Triple
T947855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet government |
E20452
|
entity |
| Predicate | censorshipPolicy |
P13641
|
FINISHED |
| Object | state censorship |
—
|
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: state censorship | Statement: [Soviet government, censorshipPolicy, state censorship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: censorshipPolicy Context triple: [Soviet government, censorshipPolicy, state censorship]
-
A.
hasCensorshipHistory
Indicates that an entity has previously been subject to censorship or involved in acts of censoring content.
-
B.
governingPolicy
Indicates that one entity serves as the authoritative policy or set of rules that directs, constrains, or regulates the behavior, operation, or decisions of another entity.
-
C.
issuesPolicyOn
chosen
Indicates that an authority or organization formally creates, approves, or enacts a policy concerning a particular subject or domain.
-
D.
supportsPolicy
Indicates that one entity endorses, backs, or is in favor of a particular policy or set of policies.
-
E.
locationPolicy
Indicates a rule or constraint governing where an entity is allowed, required, or restricted to be located.
- 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_69a493b0f2fc81908cd227480a5356a1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3be19448190a8863fce3d152430 |
completed | March 1, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69a4b29f05f481908814bd11f235e9d0 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.