Triple
T4309220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christianization of Saxony |
E94031
|
entity |
| Predicate | religionFrom |
P10604
|
FINISHED |
| Object | Germanic paganism |
—
|
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: Germanic paganism | Statement: [Christianization of Saxony, religionFrom, Germanic paganism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religionFrom Context triple: [Christianization of Saxony, religionFrom, Germanic paganism]
-
A.
subjectReligion
Indicates that the subject is associated with, practices, or adheres to a particular religion.
-
B.
religiousTarget
Indicates that an action, policy, or behavior is directed at someone or something specifically because of their religion or religious affiliation.
-
C.
bearerReligion
Indicates that a bearer (such as a person or entity) adheres to, practices, or is associated with a particular religion.
-
D.
religiousElement
Indicates that something is a component, aspect, or feature associated with a religion or religious practice.
-
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_69b3451886588190a3dd1305ea7c58dc |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b350d40748819084798058396be113 |
completed | March 12, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69b34f4a07b08190a06ada0d9cbb14fb |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:11 p.m.