Triple
T8256632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David of Sassoun |
E193085
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Armenian legendary figure |
C18629
|
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 legendary figure Context triple: [David of Sassoun, instanceOf, Armenian legendary figure]
-
A.
Mesopotamian legendary figure
A Mesopotamian legendary figure is a mythic or semi-divine personage from ancient Mesopotamian cultures whose stories, deeds, and attributes embody religious beliefs, moral values, and cosmological ideas preserved in epics, hymns, and ritual texts.
-
B.
Iranian epic hero
An Iranian epic hero is a larger-than-life figure in Persian mythology and literature who embodies ideals of bravery, honor, and loyalty while undertaking extraordinary quests that shape the fate of their people.
-
C.
Armenian saint
An Armenian saint is a holy figure recognized within the Armenian Apostolic or Armenian Catholic traditions for exemplary faith, virtue, and often martyrdom, and venerated as an intercessor and spiritual model for the faithful.
-
D.
ancient Greek figure
An ancient Greek figure is a person from ancient Greek history or mythology, such as a philosopher, statesman, warrior, or deity, who played a notable role in the cultural, political, or intellectual life of the Greek world.
-
E.
Armenian person
chosen
An Armenian person is an individual who identifies with the Armenian nation, typically sharing its historical heritage, cultural traditions, and often the Armenian language, whether living in Armenia or in the global diaspora.
- 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_69ca82dfad9c8190b8cd18fb89f50f40 |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:49 p.m.