Triple
T23177096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eanfrith of Bernicia |
E579033
|
entity |
| Predicate | religionChange |
P10604
|
FINISHED |
| Object | abandoned Christianity for 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: abandoned Christianity for paganism | Statement: [Eanfrith of Bernicia, religionChange, abandoned Christianity for paganism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religionChange Context triple: [Eanfrith of Bernicia, religionChange, abandoned Christianity for paganism]
-
A.
religiousDemographyChange
Indicates a change over time in the religious composition or affiliation distribution within a population or region.
-
B.
religiousTrend
Indicates a pattern or direction of change over time in religious beliefs, practices, or affiliations among entities.
-
C.
laterReligion
chosen
Indicates that one religion or religious affiliation chronologically follows or replaces another for the same entity.
-
D.
religiousEnvironment
Indicates the religious context, atmosphere, or setting in which an entity exists or an action takes place.
-
E.
subjectReligion
Indicates that the subject is associated with, practices, or adheres to a particular religion.
- 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_69e245fd2a388190b814c0dfa15f7148 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f6b823c8190a2d39c54e48a1001 |
completed | April 29, 2026, 4:56 a.m. |
| PD | Predicate disambiguation | batch_69ef8a041c0081909afb670d17a5aaba |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:04 p.m.