Triple
T3500062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christianization of the Balkans |
E73942
|
entity |
| Predicate | replacesReligion |
P10604
|
FINISHED |
| Object | Slavic 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: Slavic paganism | Statement: [Christianization of the Balkans, replacesReligion, Slavic paganism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacesReligion Context triple: [Christianization of the Balkans, replacesReligion, Slavic paganism]
-
A.
laterRevertedReligion
Indicates that an entity adopted a religion and then subsequently reverted or returned to a previous or different religious affiliation.
-
B.
convertedToReligion
Indicates that an entity adopted or changed to a particular religion, typically from a previous belief system or lack thereof.
-
C.
promotedReligion
Indicates that an entity actively supported, advocated for, or worked to spread a particular religion.
-
D.
sharesReligionWith
Indicates that two entities follow or are associated with the same religion or religious tradition.
-
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_69ad85cdb6e48190a335d412b9194ed8 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbbd4eb308190b84e84261ceec229 |
completed | March 8, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69adae0cd8b0819099da300af09880da |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:18 p.m.