Triple
T30318466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burial |
E771121
|
entity |
| Predicate | hasWorkOfSameAuthor |
P154273
|
FINISHED |
| Object | Luther: The Calling |
—
|
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: Luther: The Calling | Statement: [Burial, hasWorkOfSameAuthor, Luther: The Calling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkOfSameAuthor Context triple: [Burial, hasWorkOfSameAuthor, Luther: The Calling]
-
A.
hasAuthorOfSameWorkAs
Indicates that two authors are related by having written or contributed to the same work.
-
B.
workBySameAuthorAs
Indicates that two works share the same author, i.e., they were created by the same person or entity.
-
C.
complementsWorkBySameAuthor
Indicates that one work enhances, completes, or supplements another work created by the same author.
-
D.
hasAuthorOfOtherWork
chosen
Indicates that an entity is the author of another distinct work associated with the first entity.
-
E.
workInCollectionBySameAuthor
Indicates that one work is included in a collection whose other contents are by the same author as that work.
- 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_69f22489ee8481909344649bfbb92e83 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: April 29, 2026, 7:51 p.m.