Triple
T25260569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khovanshchina |
E633291
|
entity |
| Predicate | hasOrchestrationCompletedBy |
P34454
|
FINISHED |
| Object | Nikolai Rimsky-Korsakov |
—
|
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: Nikolai Rimsky-Korsakov | Statement: [Khovanshchina, hasOrchestrationCompletedBy, Nikolai Rimsky-Korsakov]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrchestrationCompletedBy Context triple: [Khovanshchina, hasOrchestrationCompletedBy, Nikolai Rimsky-Korsakov]
-
A.
hasOrchestrationBy
chosen
Indicates that something is organized, coordinated, or arranged by a specified agent or entity.
-
B.
hasOrchestration
Indicates that one entity coordinates, manages, or sequences the actions or interactions of another entity or set of entities.
-
C.
hasCompleted
Indicates that an entity has finished or successfully carried out a specified task, process, or activity.
-
D.
usesOrchestration
Indicates that one entity employs orchestration mechanisms or tools to coordinate, manage, or automate the behavior and interactions of other entities or processes.
-
E.
usesOrchestrationSimilarTo
Indicates that one entity employs an orchestration approach or mechanism that is similar to that used 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_69e75a922ad481908f4f1f884583cb42 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 21, 2026, 1:13 p.m.