Triple
T33514979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simplicissimus |
E858341
|
entity |
| Predicate | targetOfCensorshipBy |
P138544
|
FINISHED |
| Object | German Empire authorities |
—
|
NE NERFINISHED |
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: German Empire authorities | Statement: [Simplicissimus, targetOfCensorshipBy, German Empire authorities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetOfCensorshipBy Context triple: [Simplicissimus, targetOfCensorshipBy, German Empire authorities]
-
A.
censorshipTarget
chosen
Indicates that an entity is the object or focus of censorship by another entity or authority.
-
B.
censorshipReason
Indicates the justification or cause given for why certain content is suppressed, restricted, or removed.
-
C.
typeOfCensorship
Indicates the specific kind or method of censorship being applied in a given context.
-
D.
countryOfCensorshipControversy
Indicates the country in which a particular censorship-related controversy or dispute took place.
-
E.
censorshipAuthority
Indicates that one entity has the official power or responsibility to censor, restrict, or approve the information, media, or expression of another entity.
- 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_69f3497721848190978fbee5e0a526f8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe7b1c506c8190869c1a22031e0571 |
completed | May 9, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69fe796b2bdc8190a86980d44008f875 |
completed | May 9, 2026, 12:01 a.m. |
Created at: May 1, 2026, 1:39 a.m.