Triple
T33950762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khodynka Tragedy |
E870432
|
entity |
| Predicate | hasEmpire |
P17699
|
FINISHED |
| Object | Russian 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: Russian Empire | Statement: [Khodynka Tragedy, hasEmpire, Russian Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEmpire Context triple: [Khodynka Tragedy, hasEmpire, Russian Empire]
-
A.
hasConqueringEmpire
Indicates that one entity is an empire that has militarily defeated and taken control over another entity.
-
B.
hasHistoricalEmpire
Indicates that an entity once possessed, controlled, or was associated with a significant imperial power in the past.
-
C.
associatedEmpire
chosen
Indicates a relationship where one entity is linked or connected to a particular empire, typically as belonging to, originating from, or being under the influence or control of that empire.
-
D.
foundedInEmpire
Indicates that an entity (such as an organization, city, or institution) was established during the existence or rule of a specified empire.
-
E.
governingEmpire
Indicates that one entity serves as the ruling imperial power that controls or governs 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_69f3499c2d7481909c953a5010227725 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:49 a.m.