Triple
T33564487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mkhitar Gosh |
E859718
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Armenian scholar |
C61670
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: medieval Armenian scholar Context triple: [Mkhitar Gosh, instanceOf, medieval Armenian scholar]
-
A.
Persian scholar
A Persian scholar is an erudite individual from the Persian cultural sphere who engages in the study, interpretation, and advancement of knowledge in fields such as literature, philosophy, science, theology, or history.
-
B.
Byzantine scholar
A Byzantine scholar is a learned individual specializing in the language, theology, history, and culture of the Byzantine Empire, often engaging in the preservation, interpretation, and commentary of classical and Christian texts.
-
C.
Ottoman scholar
An Ottoman scholar is an educated intellectual of the Ottoman Empire who engaged in religious, legal, scientific, or literary studies, often serving as a jurist, teacher, or advisor within the empire’s administrative and cultural institutions.
-
D.
Syriac grammarian
A Syriac grammarian is a scholar who studies, analyzes, and explains the structure, rules, and usage of the Syriac language, often through the composition of grammatical treatises and teaching materials.
-
E.
6th-century scholar
A 6th-century scholar is an educated individual of the 500s CE who engaged in the study, preservation, and interpretation of knowledge—often in fields like theology, philosophy, law, or classical texts—within the cultural and intellectual traditions of their time.
- F. None of above. chosen
Provenance (1 batch)
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_69f3497c1d288190a844ea699914e038 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:40 a.m.