Triple
T33950758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khodynka Tragedy |
E870432
|
entity |
| Predicate | hasCoronationEvent |
P28655
|
FINISHED |
| Object | Coronation of Nicholas II |
E249089
|
NE 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: Coronation of Nicholas II | Statement: [Khodynka Tragedy, hasCoronationEvent, Coronation of Nicholas II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoronationEvent Context triple: [Khodynka Tragedy, hasCoronationEvent, Coronation of Nicholas II]
-
A.
hasCoronationRitual
Indicates that an entity is associated with a specific formal ceremony or set of rites used to crown or inaugurate a ruler or leader.
-
B.
coronationEvent
chosen
Indicates the event in which a person is formally invested with royal authority and crowned as a monarch.
-
C.
hasEnthronementCeremony
Indicates that an entity formally assumes a position of authority or rulership through an official enthronement ceremony.
-
D.
hasCoronationSubject
Indicates that an entity serves as the subject (the person or figure being crowned) in a coronation event.
-
E.
coronationStatus
Indicates the current stage or condition of an entity’s coronation process, such as whether it is pending, ongoing, or completed.
- F. None of above.
Provenance (4 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_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36ae3828ec8190a8f902fac693a647 |
completed | June 20, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:49 a.m.