Triple
T28880241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Avarayr |
E732395
|
entity |
| Predicate | VardanMamikonianRole |
P86439
|
FINISHED |
| Object | sparapet of Armenia |
—
|
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: sparapet of Armenia | Statement: [Battle of Avarayr, VardanMamikonianRole, sparapet of Armenia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: VardanMamikonianRole Context triple: [Battle of Avarayr, VardanMamikonianRole, sparapet of Armenia]
-
A.
ArmenianCommander
chosen
Indicates that an individual serves as a military commander associated with Armenia.
-
B.
MaadimVallisRole
Indicates that something serves as or is characterized by the functional role or significance of Maadim Vallis within a broader system, context, or process.
-
C.
CorwinRole
Indicates that an entity holds or is assigned a specific role or function in relation to Corwin.
-
D.
roleForVarys
Indicates that a particular role, position, or function is assigned to or associated with Varys.
-
E.
sonRole
Indicates that one entity holds the role or relationship of a son with respect to another entity.
- 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 7:43 a.m.