Triple
T33514948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simplicissimus |
E858341
|
entity |
| Predicate | finalPublication |
P44445
|
FINISHED |
| Object | 1967 |
—
|
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: 1967 | Statement: [Simplicissimus, finalPublication, 1967]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalPublication Context triple: [Simplicissimus, finalPublication, 1967]
-
A.
finalPublicationDate
chosen
Indicates the date on which a work is officially and definitively published in its final form.
-
B.
publicationCompleted
Indicates that the process of publishing an item (such as a document, work, or release) has been fully finished and made officially available.
-
C.
endedPublication
Indicates that an entity has ceased or terminated its publication activity, marking the end of its publishing period.
-
D.
publishedEdition
Indicates that one entity is a specific edition or version that has been formally published of another work or resource.
-
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_69f3497721848190978fbee5e0a526f8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe2f078c24819082ba396b56f02808 |
completed | May 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69fe228fe1988190baf3bb34897f3dbe |
completed | May 8, 2026, 5:51 p.m. |
Created at: May 1, 2026, 1:39 a.m.