Triple
T9404465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Death of Boris |
E226549
|
entity |
| Predicate | isKeySceneIn |
P47737
|
FINISHED |
| Object | Russian operatic repertoire |
—
|
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: Russian operatic repertoire | Statement: [Death of Boris, isKeySceneIn, Russian operatic repertoire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isKeySceneIn Context triple: [Death of Boris, isKeySceneIn, Russian operatic repertoire]
-
A.
containsScene
chosen
Indicates that one entity (typically a media item or narrative work) includes or features a particular scene as part of its content.
-
B.
hasInfluenceFromScene
Indicates that something is affected, shaped, or guided by the characteristics or context of a particular scene.
-
C.
isInKey
Indicates that something is located within, or belongs to, a specified key or key-based grouping in a structured context.
-
D.
performedInSceneType
Indicates that an action or event was carried out within a scene of a specified type or category.
-
E.
partOfScene
Indicates that one entity functions as a component or element within a larger scene or setting involving 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_69ca843170f88190800a8ab2b5fc568e |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd51c125dc8190a6438cf0ee23e7a9 |
completed | April 1, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69cca54c37f88190bddccf28e5fe5c84 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:46 p.m.