Triple
T36501711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barskhan tribe |
E899346
|
entity |
| Predicate | transitionOfReligion |
P11201
|
FINISHED |
| Object | from Tengriism to Islam |
—
|
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: from Tengriism to Islam | Statement: [Barskhan tribe, transitionOfReligion, from Tengriism to Islam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transitionOfReligion Context triple: [Barskhan tribe, transitionOfReligion, from Tengriism to Islam]
-
A.
religionBeforeReformation
Indicates that an entity’s religious affiliation or practice existed or was established prior to the historical period known as the Reformation.
-
B.
convertedToReligion
chosen
Indicates that an entity adopted or changed to a particular religion, typically from a previous belief system or lack thereof.
-
C.
religiousConversionPeriod
Indicates the time span during which an entity undergoes or is involved in a process of religious conversion.
-
D.
typicalReligionAfterReformation
Indicates the predominant religion an entity adhered to following the Reformation period.
-
E.
laterReligion
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_69f76e5b92088190933afda3f7531dd4 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff8ba3f8248190bbdf8e7ec2b35093 |
completed | May 9, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69ff8b41ba988190a7332e8317d10f09 |
completed | May 9, 2026, 7:30 p.m. |
Created at: May 3, 2026, 4:10 p.m.