Triple
T9572533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volga Bulgaria historical area |
E230958
|
entity |
| Predicate | religiousCenter |
P1191
|
FINISHED |
| Object | Bolghar |
E807661
|
NE 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: Bolghar | Statement: [Volga Bulgaria historical area, religiousCenter, Bolghar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bolghar Context triple: [Volga Bulgaria historical area, religiousCenter, Bolghar]
-
A.
Bolghar
chosen
Bolghar was the medieval capital city of Volga Bulgaria, an important political, commercial, and cultural center on the Volga River.
-
B.
Tsakhurs
Tsakhurs are a Northeast Caucasian ethnic group traditionally inhabiting mountainous regions of present-day Azerbaijan and Dagestan, known for their distinct language and rich folk culture.
-
C.
Barya
Barya is an alternative name for the Nara people, an ethnic group primarily inhabiting parts of Eritrea.
-
D.
Balkar
Balkar is a Turkic language spoken primarily by the Balkar people in the North Caucasus region of Russia.
-
E.
Balya
Balya is a small town and district in western Turkey known historically for its mining activities and rural character.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca847f22188190a56e4a97625bef22 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd998d79cc8190b94e5953915a5fa4 |
completed | April 1, 2026, 10:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1614f33108190901e3037654c50ab |
completed | April 4, 2026, 7:06 p.m. |
Created at: March 30, 2026, 8:04 p.m.