Triple
T4915283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | County of Lippe |
E110331
|
entity |
| Predicate | mainReligionAfterReformation |
P10604
|
FINISHED |
| Object | Protestantism |
—
|
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: Protestantism | Statement: [County of Lippe, mainReligionAfterReformation, Protestantism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainReligionAfterReformation Context triple: [County of Lippe, mainReligionAfterReformation, Protestantism]
-
A.
religionBeforeReformation
Indicates that an entity’s religious affiliation or practice existed or was established prior to the historical period known as the Reformation.
-
B.
postReformationDenomination
Indicates that one religious group or entity belongs to, or is associated with, a Christian denomination that emerged after the Protestant Reformation.
-
C.
religiousReformImpact
Indicates the effect that a religious reform has on beliefs, practices, institutions, or social structures.
-
D.
underwentReformation
Indicates that an entity experienced a significant process of change, restructuring, or reform that altered its previous state or practices.
-
E.
laterReligion
chosen
Indicates that one religion or religious affiliation chronologically follows or replaces another for the same entity.
- 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_69bd44132b94819088522d92beaadc78 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6fa404f881908b4f983983ac7076 |
completed | March 20, 2026, 4:02 p.m. |
| PD | Predicate disambiguation | batch_69bd6c325e188190823836d79934e9bc |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:29 p.m.