Triple
T19143088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NO-DO |
E468605
|
entity |
| Predicate | censorshipApplied |
P74007
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [NO-DO, censorshipApplied, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: censorshipApplied Context triple: [NO-DO, censorshipApplied, yes]
-
A.
censorshipReason
Indicates the justification or cause given for why certain content is suppressed, restricted, or removed.
-
B.
censorshipLevel
Indicates the degree or strictness of control, suppression, or restriction applied to information, media, or expression.
-
C.
wasCensored
chosen
Indicates that an entity’s content, expression, or communication was suppressed, altered, or restricted by an authority or controlling party.
-
D.
censorshipAuthority
Indicates that one entity has the official power or responsibility to censor, restrict, or approve the information, media, or expression of another entity.
-
E.
censorshipEvent
Indicates an event in which information, expression, or communication is suppressed, restricted, or altered by some controlling authority or mechanism.
- 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e976e340819098efccc30b2eef0e |
completed | April 20, 2026, 8:53 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b475d88190a8c15e8eb01dbfef |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.