Triple
T30941766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ossietzky treason trial |
E788280
|
entity |
| Predicate | publicationInvolved |
P60109
|
FINISHED |
| Object | Die Weltbühne |
—
|
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: Die Weltbühne | Statement: [Ossietzky treason trial, publicationInvolved, Die Weltbühne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicationInvolved Context triple: [Ossietzky treason trial, publicationInvolved, Die Weltbühne]
-
A.
involvesPublication
chosen
Indicates that an action, event, or process includes or is associated with a specific publication as a relevant component.
-
B.
publicationActivity
Indicates the act or process of producing and disseminating a work (such as a document, article, or media item) to an audience.
-
C.
publicationOpus
Indicates that a work or opus has been published, linking the creative work to its publication event or status.
-
D.
publicationMention
Indicates that one entity (such as a document, statement, or record) explicitly references or cites a particular publication.
-
E.
publishedDocument
Indicates that an entity has formally issued or made a document publicly available.
- 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_69f224c180f88190ad177372ee02b7e2 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe38be079c8190a240191ac0e73e3a |
completed | May 8, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69fe350344508190930de2218156ca02 |
completed | May 8, 2026, 7:09 p.m. |
Created at: April 29, 2026, 8:53 p.m.