Triple
T31217688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Song of the Varangian Guest |
E795915
|
entity |
| Predicate | operaActContext |
P27848
|
FINISHED |
| Object | early act of Boris Godunov |
—
|
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: early act of Boris Godunov | Statement: [Song of the Varangian Guest, operaActContext, early act of Boris Godunov]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operaActContext Context triple: [Song of the Varangian Guest, operaActContext, early act of Boris Godunov]
-
A.
operaAct
Indicates that an entity performs in or takes part in an act (segment) of an opera performance.
-
B.
operaPremiereContext
Indicates the circumstances or setting (such as time, place, or event) in which an opera had its premiere performance.
-
C.
operaEnÁmbito
Indicates that an entity operates, functions, or carries out its activities within a specified domain, field, or scope.
-
D.
actCountInOpera
Indicates the number of acts that occur within a given opera.
-
E.
operaComponent
chosen
Indicates that one entity is a constituent part or section of an opera associated with the other 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_69f224d9d52c8190a61f68ded37fa755 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff9d9cb4f8819083682be3c483b599 |
completed | May 9, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69ff9c38bf9c8190bbb85b32f3ae3d2e |
completed | May 9, 2026, 8:42 p.m. |
Created at: April 29, 2026, 9:10 p.m.