Triple
T5510977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reformation in the Palatinate |
E144563
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in the 16th century |
C14531
|
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: event in the 16th century Context triple: [Reformation in the Palatinate, instanceOf, event in the 16th century]
-
A.
15th-century event
A 15th-century event is a historically significant occurrence that took place between 1401 and 1500, shaped by and contributing to the political, social, cultural, or technological transformations of that period.
-
B.
16th-century conflict
chosen
A 16th-century conflict is a historically documented military, political, or religious struggle that occurred between 1501 and 1600, involving organized groups or states and significantly influencing the social and geopolitical landscape of the early modern period.
-
C.
16th-century council
A 16th-century council is a formal assembly of political, religious, or civic authorities convened during the 1500s to deliberate and decide on matters of governance, doctrine, law, or public policy.
-
D.
13th-century event
A 13th-century event is any significant occurrence, development, or happening that took place between the years 1201 and 1300 CE.
-
E.
15th-century document
A 15th-century document is a written or printed record created between 1401 and 1500, reflecting the political, religious, economic, or cultural contexts of late medieval and early Renaissance societies.
- 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_69c008f6b5048190a09064116062cf69 |
completed | March 22, 2026, 3:21 p.m. |
Created at: March 22, 2026, 3:33 p.m.