Triple
T6499155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchy of Prussia |
E148834
|
entity |
| Predicate | reformation |
P41349
|
FINISHED |
| Object | Lutheran Reformation adopted |
—
|
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: Lutheran Reformation adopted | Statement: [Duchy of Prussia, reformation, Lutheran Reformation adopted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reformation Context triple: [Duchy of Prussia, reformation, Lutheran Reformation adopted]
-
A.
underwentReformation
chosen
Indicates that an entity experienced a significant process of change, restructuring, or reform that altered its previous state or practices.
-
B.
religionBeforeReformation
Indicates that an entity’s religious affiliation or practice existed or was established prior to the historical period known as the Reformation.
-
C.
reformationYear
Indicates the year in which an entity underwent a significant reform, restructuring, or reorganization.
-
D.
reformationPlace
Indicates the place where an entity undergoes reformation, restructuring, or significant organizational change.
-
E.
religiousReformImpact
Indicates the effect that a religious reform has on beliefs, practices, institutions, or social structures.
- 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_69c687e9ad288190bae5bcac9c8ac855 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c69f386aa08190bfc8592a92ec6339 |
completed | March 27, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69c68ab714908190aa7c2fbf64078e15 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:41 p.m.