Triple
T32847165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wessobrunn |
E840129
|
entity |
| Predicate | hasWrittenWorkOrigin |
P175176
|
FINISHED |
| Object | Wessobrunn Prayer |
—
|
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: Wessobrunn Prayer | Statement: [Wessobrunn, hasWrittenWorkOrigin, Wessobrunn Prayer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWrittenWorkOrigin Context triple: [Wessobrunn, hasWrittenWorkOrigin, Wessobrunn Prayer]
-
A.
hasWrittenWorkType
Indicates that an entity (typically a written work) is associated with a specific type or category of written work (such as novel, article, report, etc.).
-
B.
hasCreatedWorksFor
Indicates that one entity has produced or created works (such as art, documents, or products) on behalf of or for the benefit of another entity.
-
C.
hasWrittenAbout
Indicates that one entity has authored content or material discussing, analyzing, or referencing another entity.
-
D.
hasAuthorOfOtherWork
Indicates that an entity is the author of another distinct work associated with the first entity.
-
E.
hasCatalogedWorkOn
Indicates that an entity has formally recorded, listed, or documented another entity as a work within a catalog or collection.
- F. None of above. chosen
Provenance (4 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_69f349412c78819084459850e11d29f7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6cee547108190ad3bc84297d8f516 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6ce6c76bc8190b865343d3f5810c9 |
completed | May 3, 2026, 4:26 a.m. |
Created at: May 1, 2026, 1:17 a.m.