Triple
T29456107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Sardarabad |
E747104
|
entity |
| Predicate | strategicObjectiveOfArmenians |
P129227
|
FINISHED |
| Object | defend Yerevan |
—
|
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: defend Yerevan | Statement: [Battle of Sardarabad, strategicObjectiveOfArmenians, defend Yerevan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strategicObjectiveOfArmenians Context triple: [Battle of Sardarabad, strategicObjectiveOfArmenians, defend Yerevan]
-
A.
strategicObjectiveOttoman
Indicates that one entity serves as or relates to a strategic objective or goal specifically concerning the Ottoman Empire.
-
B.
strategicObjectiveAfghan
Indicates that an entity has a strategic objective specifically related to Afghanistan or Afghan affairs.
-
C.
strategicObjectiveOfIsrael
Indicates that something is a strategic objective pursued by Israel.
-
D.
militaryObjectiveOf
chosen
Indicates that something serves as a military target, goal, or purpose specifically associated with a given actor or force.
-
E.
aimOfByzantines
Indicates the goal or objective pursued by the Byzantines in a given context.
- 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_69f67f7efc3c8190986d2d95b7a23729 |
completed | May 2, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 28, 2026, 3:36 p.m.