Triple
T31993202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Echmiadzin (1804) |
E816922
|
entity |
| Predicate | opposingEmpire2 |
P138442
|
FINISHED |
| Object | Qajar Empire |
—
|
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: Qajar Empire | Statement: [Battle of Echmiadzin (1804), opposingEmpire2, Qajar Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposingEmpire2 Context triple: [Battle of Echmiadzin (1804), opposingEmpire2, Qajar Empire]
-
A.
opposingForce
Indicates a relationship where one entity actively resists, counters, or works against the actions, goals, or influence of another entity.
-
B.
opposingAlliance
Indicates that two entities belong to rival or mutually opposed alliances or factions.
-
C.
opponentMonarch
Indicates that one monarch stands in an opposing or adversarial position to another monarch, typically in conflict or competition.
-
D.
opposedWar
Indicates that an entity actively resisted, disagreed with, or worked against a particular war or military conflict.
-
E.
opposingUnits
chosen
Indicates that two units are in opposition to each other, such as being on rival sides, conflicting forces, or competing entities within 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_69f348f8002081909a3588758ba94afb |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 1, 2026, 12:13 a.m.