Triple
T4548235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luther’s Sermon on Indulgences and Grace |
E110095
|
entity |
| Predicate | placeInLutherCorpus |
P57651
|
FINISHED |
| Object | early Reformation writing |
—
|
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: early Reformation writing | Statement: [Luther’s Sermon on Indulgences and Grace, placeInLutherCorpus, early Reformation writing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeInLutherCorpus Context triple: [Luther’s Sermon on Indulgences and Grace, placeInLutherCorpus, early Reformation writing]
-
A.
positionInBible
Indicates the specific location or order of a passage, verse, or book within the structured sequence of the Bible.
-
B.
LutherAlias
Indicates that one name or label is an alternative designation or alias for Luther.
-
C.
placeInApuleiusCorpus
Indicates that a given text or passage occurs within the works that make up the Apuleius corpus.
-
D.
reformationPlace
Indicates the place where an entity undergoes reformation, restructuring, or significant organizational change.
-
E.
positionAmongGospels
Indicates the numerical order or placement of a given gospel within the sequence of all gospels.
- 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_69bd4412524c8190be5bcc9ddee91848 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd57f272248190983ae439bd0ac0cc |
completed | March 20, 2026, 2:21 p.m. |
| PD | Predicate disambiguation | batch_69bd5220e40481908ca2d7e2c43d8531 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56f6e75481909c487a94a2c2d0ba |
completed | March 20, 2026, 2:17 p.m. |
Created at: March 20, 2026, 1:05 p.m.