Triple
T3280410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Origin of the World |
E68857
|
entity |
| Predicate | hasOnlineCensorshipIncidents |
P17134
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The Origin of the World, hasOnlineCensorshipIncidents, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnlineCensorshipIncidents Context triple: [The Origin of the World, hasOnlineCensorshipIncidents, true]
-
A.
hasCensorshipHistory
chosen
Indicates that an entity has previously been subject to censorship or involved in acts of censoring content.
-
B.
networkCensorshipIssues
Indicates that there are problems or restrictions in accessing content or services due to censorship imposed on a network.
-
C.
censorshipStatusAtTime
Indicates the censorship status of something at a specific point in time, capturing whether and how it was censored then.
-
D.
censorshipReason
Indicates the justification or cause given for why certain content is suppressed, restricted, or removed.
-
E.
revisedVersionCensorshipStatus
Indicates the censorship or restriction status applied to a revised version of some original content.
- 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_69ad859c463481909ca4be267336c290 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0166c8c81909cb0a580ef319be3 |
completed | March 8, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69ada420167c81909b6e2702db296d9e |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.