Triple
T9304484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wittenberg Concord negotiations |
E223847
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Protestant Reformation event |
C3445
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Protestant Reformation event Context triple: [Wittenberg Concord negotiations, instanceOf, Protestant Reformation event]
-
A.
Protestant reform measure
A Protestant reform measure is a specific policy, decree, or action implemented to align religious, political, or social practices with Protestant theological principles and church governance.
-
B.
Christian reform movement
chosen
A Christian reform movement is a religious initiative within Christianity aimed at renewing faith, correcting perceived doctrinal or moral errors, and transforming church practices or social structures in light of biblical principles.
-
C.
event of the French Wars of Religion
An event of the French Wars of Religion is a historically specific occurrence—such as a battle, edict, massacre, negotiation, or political maneuver—directly related to the religious and civil conflicts between Catholics and Protestants in France between 1562 and 1598.
-
D.
Reformation-era theologian
A Reformation-era theologian is a religious scholar from the 16th-century Protestant or Catholic reform movements who developed, debated, and systematized doctrines that reshaped Western Christianity.
-
E.
event in church history
An event in church history is a significant occurrence or development within the life of the Christian church that influences its doctrine, practice, structure, or relationship with society over time.
- F. None of above.
Provenance (1 batch)
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_69ca8424d0f08190831e2e93c6533aeb |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:36 p.m.