Triple
T28880242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Avarayr |
E732395
|
entity |
| Predicate | VardanMamikonianStatus |
P166006
|
FINISHED |
| Object | killed in battle |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: killed in battle | Statement: [Battle of Avarayr, VardanMamikonianStatus, killed in battle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: VardanMamikonianStatus Context triple: [Battle of Avarayr, VardanMamikonianStatus, killed in battle]
-
A.
statusInArmenianChurch
Indicates the role, position, or standing that an entity holds within the Armenian Church.
-
B.
currentCatholicosOfAllArmenians
Indicates that one entity is the person who currently holds the office of Catholicos of All Armenians in relation to the Armenian Apostolic Church.
-
C.
modernStatus
Indicates the current or contemporary condition, classification, or standing of an entity in the present time.
-
D.
vowStatus
Indicates the current state or condition of a commitment or promise made between entities, such as whether it is active, fulfilled, or broken.
-
E.
statusInSira
Indicates the status or standing that an entity holds within the Sira system or classification.
- F. None of above. chosen
Provenance (4 batches)
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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65bb75cd08190bbdb63c093ad6210 |
completed | May 2, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65b136b30819090cf59fb772f35f1 |
completed | May 2, 2026, 8:14 p.m. |
Created at: April 28, 2026, 7:43 a.m.