Triple
T14560793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tigranes the Great |
E341658
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Armenian ruler |
C22235
|
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: ancient Armenian ruler Context triple: [Tigranes the Great, instanceOf, ancient Armenian ruler]
-
A.
King of Armenia
chosen
The King of Armenia is the sovereign ruler of the Armenian kingdom, holding supreme political, military, and ceremonial authority over its territories and people.
-
B.
Armenian prince
An Armenian prince is a nobleman of Armenia’s historical aristocracy, often ruling a principality or region and serving as a military and political leader within the Armenian kingdom or under foreign suzerainty.
-
C.
King of Urartu
The King of Urartu is the sovereign ruler of the ancient kingdom of Urartu, responsible for governing its territories, commanding its military, overseeing religious and administrative affairs, and representing the state in foreign relations.
-
D.
ancient Near Eastern ruler
An ancient Near Eastern ruler is a sovereign leader who governed a city-state or empire in regions such as Mesopotamia, Anatolia, the Levant, or Persia, wielding political, military, economic, and often religious authority.
-
E.
Sasanian king
A Sasanian king is the sovereign ruler of the Sasanian Empire, wielding supreme political, military, and religious authority over its territories and subjects.
- 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_69d822dcc6248190bed689984bceb0e2 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:23 a.m.