Triple
T31594053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patmutʻiwn Hayocʻ |
E806174
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Armenian chronicle |
C29154
|
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: Armenian chronicle Context triple: [Patmutʻiwn Hayocʻ, instanceOf, Armenian chronicle]
-
A.
Byzantine chronicle
A Byzantine chronicle is a historical narrative, often arranged annalistically, that records events of the Byzantine Empire and surrounding regions, typically blending factual reporting with religious interpretation and classical traditions.
-
B.
national epic of Armenia
The national epic of Armenia is a foundational heroic narrative that embodies the Armenian people's historical struggles, cultural values, and collective identity through legendary figures and mythic events.
-
C.
monastic chronicle
chosen
A monastic chronicle is a historical narrative compiled and maintained by monks within a religious community, recording significant events, religious observances, and local or wider affairs over time.
-
D.
Irish chronicle
An Irish chronicle is a medieval or early modern annalistic record, typically compiled by monastic or learned authors in Ireland, that documents events year by year such as political happenings, deaths, battles, and notable natural phenomena.
-
E.
medieval Armenian kingdom
A medieval Armenian kingdom is a historically situated political entity in the Armenian Highlands, characterized by Armenian dynastic rule, Christian cultural identity, and feudal socio-political structures interacting with neighboring empires.
- F. None of above.
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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:29 p.m.