Triple
T9251957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khazar Khaganate |
E222345
|
entity |
| Predicate | religiousConversionOfElite |
P28896
|
FINISHED |
| Object | 8th century |
—
|
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: 8th century | Statement: [Khazar Khaganate, religiousConversionOfElite, 8th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousConversionOfElite Context triple: [Khazar Khaganate, religiousConversionOfElite, 8th century]
-
A.
convertedToReligion
Indicates that an entity adopted or changed to a particular religion, typically from a previous belief system or lack thereof.
-
B.
religiousConversionPeriod
chosen
Indicates the time span during which an entity undergoes or is involved in a process of religious conversion.
-
C.
laterRevertedReligion
Indicates that an entity adopted a religion and then subsequently reverted or returned to a previous or different religious affiliation.
-
D.
convertedToIslamWith
Indicates that one entity adopted Islam through the influence, guidance, or involvement of another entity.
-
E.
religionOfConquerors
Indicates that the specified religion is practiced or upheld by the conquering group or power in a given context.
- 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_69ca841d2b18819089f9faf5b2c2aec0 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd05fb1454819098f452846ca4ca61 |
completed | April 1, 2026, 11:48 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4e79e48190b3200247f4624867 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:31 p.m.