Triple
T26458396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vrtanes I of Armenia |
E665556
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 4th-century Armenian person |
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: 4th-century Armenian person Context triple: [Vrtanes I of Armenia, instanceOf, 4th-century Armenian person]
-
A.
4th-century Iranian person
A 4th-century Iranian person is an individual from the Iranian cultural or political sphere who lived during the 300s CE, typically under the Sasanian Empire or related Iranian polities.
-
B.
4th-century Roman person
A 4th-century Roman person is an individual who lived within the Roman Empire during the 300s CE, shaped by the era’s political transformations, military conflicts, and the growing influence of Christianity.
-
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.
4th-century Christian bishop
A 4th-century Christian bishop was a high-ranking church leader responsible for overseeing a Christian community, defending orthodoxy amid theological controversies, and guiding the church through the transition from persecution to imperial favor.
-
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_69ee883e812c8190a9b5a9cdb87fee5e |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 27, 2026, 12:10 a.m.