Triple
T30530088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Artaxata |
E776969
|
entity |
| Predicate | primaryArmenianCommander |
P86439
|
FINISHED |
| Object | Tigranes II of Armenia |
E341658
|
NE 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: Tigranes II of Armenia | Statement: [Battle of Artaxata, primaryArmenianCommander, Tigranes II of Armenia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryArmenianCommander Context triple: [Battle of Artaxata, primaryArmenianCommander, Tigranes II of Armenia]
-
A.
ArmenianCommander
chosen
Indicates that an individual serves as a military commander associated with Armenia.
-
B.
PersianCommander
Indicates that an entity serves as a military commander for, or in the context of, the Persian forces or Persian polity.
-
C.
ArabCommander
Indicates that the subject serves as a military commander associated with Arab forces or entities.
-
D.
ParthianCommander
Indicates that an entity serves as a military commander within the Parthian context or forces.
-
E.
ArgiveCommander
Indicates a relationship where an entity holds the role or status of a commander associated with Argos or the Argives.
- F. None of above.
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_69f2249c11508190ae7e955755ccfb01 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a02f441bd408190923b6b68adee8fde |
completed | May 12, 2026, 9:34 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a28bbc23584819081b8ce1626ee28b7 |
completed | June 10, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_6a02f3c1e64881908569423c9f298f26 |
completed | May 12, 2026, 9:32 a.m. |
Created at: April 29, 2026, 8:18 p.m.