Triple
T28947869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ayrarat |
E730928
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | province of ancient Armenia |
C54135
|
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: province of ancient Armenia Context triple: [Ayrarat, instanceOf, province of ancient Armenia]
-
A.
province of Armenia
A province of Armenia is an administrative territorial unit within the Republic of Armenia, governed by a regional authority and comprising multiple communities, towns, and villages.
-
B.
Assyrian province
An Assyrian province is an administrative territorial unit of the ancient Assyrian Empire, governed by an appointed official responsible for taxation, military conscription, and local order under the authority of the Assyrian king.
-
C.
Caucasian Albania
Caucasian Albania was an ancient kingdom and later province in the eastern Caucasus, roughly corresponding to parts of modern Azerbaijan and southern Dagestan, known from classical and early medieval sources.
-
D.
region of the Armenian Highlands
chosen
A region of the Armenian Highlands is a geographically defined area within this mountainous plateau characterized by shared physical features, historical context, and cultural significance.
-
E.
Sasanian province
A Sasanian province was an administrative territorial unit of the Sasanian Empire, governed by appointed officials responsible for taxation, justice, and military organization within its boundaries.
- 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_69f043eb9bcc819091ac7b07aecb6475 |
completed | April 28, 2026, 5:21 a.m. |
Created at: April 28, 2026, 8:41 a.m.