Triple
T17182708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jan Wagner |
E417020
|
entity |
| Predicate | hasWrittenTextOn |
P14097
|
FINISHED |
| Object | modern German-language poetry |
—
|
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: modern German-language poetry | Statement: [Jan Wagner, hasWrittenTextOn, modern German-language poetry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWrittenTextOn Context triple: [Jan Wagner, hasWrittenTextOn, modern German-language poetry]
-
A.
isWritten
Indicates that a text, document, or content has been created or recorded in written form by an agent.
-
B.
hasWrittenFor
Indicates that one entity has created written content (such as articles, stories, or texts) for or on behalf of another entity, typically a publication, organization, or platform.
-
C.
areWrittenOn
Indicates that one entity serves as a surface or medium on which another entity is inscribed, recorded, or written.
-
D.
writtenTo
Indicates that something has been addressed or directed in written form to a particular recipient.
-
E.
hasWrittenAbout
chosen
Indicates that one entity has authored content or material discussing, analyzing, or referencing 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_69d886d5f34c8190b24564dfaa63f3fb |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42d934ec08190acc47073758ac3c0 |
completed | April 19, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69e383141ae0819096acd71683637cbc |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:37 a.m.