Triple
T10556101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | coronation of Nicholas II of Russia |
E249089
|
entity |
| Predicate | featuredRitual |
P29760
|
FINISHED |
| Object | anointing of the emperor |
—
|
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: anointing of the emperor | Statement: [coronation of Nicholas II of Russia, featuredRitual, anointing of the emperor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredRitual Context triple: [coronation of Nicholas II of Russia, featuredRitual, anointing of the emperor]
-
A.
hasRituals
Indicates that one entity performs, observes, or is associated with specific rituals in relation to another entity or context.
-
B.
hasRitual
Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial practice.
-
C.
appearsInRitual
chosen
Indicates that an entity is included, featured, or participates as a component or element within a specific ritual.
-
D.
viewOnRitual
Indicates a subject’s perspective, attitude, or interpretation regarding a particular ritual or ritual practice.
-
E.
functionInRitual
Indicates that an entity serves a specific role or performs a particular function within a ritual.
- 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_69d381c733c08190ab1dd6239f5f34ae |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d52712a9988190bf63e7c47f6e6fc1 |
completed | April 7, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69d518fa0b4081909bffc936d78bd77b |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:35 p.m.