Triple
T10108065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glavlit |
E218173
|
entity |
| Predicate | controlledContent |
P61102
|
FINISHED |
| Object | newspapers |
—
|
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: newspapers | Statement: [Glavlit, controlledContent, newspapers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlledContent Context triple: [Glavlit, controlledContent, newspapers]
-
A.
controlled
Indicates that one entity has power, authority, or influence to direct, regulate, or determine the behavior, actions, or state of another entity.
-
B.
contentAccess
Indicates that one entity is permitted to retrieve, view, or otherwise use the content provided or controlled by another entity.
-
C.
regulatesContentFor
chosen
Indicates that one entity controls, manages, or sets rules governing the content produced, shared, or accessed by another entity.
-
D.
censorshipReason
Indicates the justification or cause given for why certain content is suppressed, restricted, or removed.
-
E.
controlledAfter
Indicates that one entity gains or maintains control over another entity only after a specified time, event, or condition has occurred.
- 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_69ca83da93fc8190b54e44bc2b34857c |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cdd0ca7f7c8190ba7ed37940aa933d |
completed | April 2, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9ed7e48190aa132ef8a69b49f9 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:03 p.m.