Triple
T29456085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Sardarabad |
E747104
|
entity |
| Predicate | commanderForArmenians |
P86439
|
FINISHED |
| Object | Movses Silikyan |
—
|
NE NERFINISHED |
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: Movses Silikyan | Statement: [Battle of Sardarabad, commanderForArmenians, Movses Silikyan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commanderForArmenians Context triple: [Battle of Sardarabad, commanderForArmenians, Movses Silikyan]
-
A.
ArmenianCommander
chosen
Indicates that an individual serves as a military commander associated with Armenia.
-
B.
commanderOfTurkishForces
Indicates that one entity serves as the commanding officer of Turkish military forces associated with another entity.
-
C.
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.
-
D.
commanderOfGreekForces
Indicates that one entity serves as the commanding leader of the Greek military forces in a given context or conflict.
-
E.
commanderForBulgaria
Indicates that an entity serves or has served in the role of commander on behalf of, or in the service of, Bulgaria.
- F. None of above.
Provenance (3 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_69f0a7a230488190b44a97fe3d16f731 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 28, 2026, 3:36 p.m.