Triple
T32000298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taibugid dynasty |
E817106
|
entity |
| Predicate | conquest |
P8503
|
FINISHED |
| Object | Russian conquest of the Siberian Khanate |
—
|
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: Russian conquest of the Siberian Khanate | Statement: [Taibugid dynasty, conquest, Russian conquest of the Siberian Khanate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conquest Context triple: [Taibugid dynasty, conquest, Russian conquest of the Siberian Khanate]
-
A.
conquestEvent
chosen
Indicates an event in which one party gains control over another entity or territory through force or domination.
-
B.
typeOfConquest
Indicates the specific manner or category of conquest by which one entity gains control over or dominance of another.
-
C.
afterConquest
Indicates that one event, state, or condition occurs subsequent to and as a result of a conquest having taken place.
-
D.
conquestCampaign
Indicates a military or strategic campaign undertaken with the goal of conquering and taking control of a target entity or territory.
-
E.
afterConquestBy
Indicates that one entity exists in a state, condition, or situation that occurs subsequent to and as a result of being conquered by 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_69f348f8ce388190ae84376b1f348f12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b3fbfe4c8190bc1591394bc8ebb4 |
completed | May 3, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:14 a.m.