Triple
T21146837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Great Bulgar Khanate |
E521077
|
entity |
| Predicate | ethnoGeneticRole |
P143053
|
FINISHED |
| Object | precursor of Volga Bulgars |
—
|
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: precursor of Volga Bulgars | Statement: [Old Great Bulgar Khanate, ethnoGeneticRole, precursor of Volga Bulgars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnoGeneticRole Context triple: [Old Great Bulgar Khanate, ethnoGeneticRole, precursor of Volga Bulgars]
-
A.
hasEthnoreligiousRole
Indicates that an entity holds a role, function, or status defined by a combined ethnic and religious identity within a given context.
-
B.
EthnicaType
Indicates a relationship where an entity is classified according to a specific ethnic category or type.
-
C.
ethnolinguisticGroups
Indicates a relationship where groups are categorized or associated based on shared ethnic and linguistic characteristics.
-
D.
ethnogenesisRegion
Indicates the geographic region where the formation or emergence of an ethnic group took place.
-
E.
ethnographicRole
Indicates the role or function an entity holds within an ethnographic context, such as a cultural, social, or research-related position.
- F. None of above. chosen
Provenance (4 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_69e0b50c6a848190a4e525a77a319b8a |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e723fdc25481909d6648e09b069c41 |
completed | April 21, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69e5f5f8a5bc819081918c7fa8e4496d |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f993240c8190847c0b08e65726c8 |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 2:58 p.m.