Triple

T32910646
Position Surface form Disambiguated ID Type / Status
Subject Leningrad State Academic Maly Opera Theatre E841865 entity
Predicate revertedNameTo P16337 FINISHED
Object Mikhailovsky Theatre 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: Mikhailovsky Theatre | Statement: [Leningrad State Academic Maly Opera Theatre, revertedNameTo, Mikhailovsky Theatre]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: revertedNameTo
Context triple: [Leningrad State Academic Maly Opera Theatre, revertedNameTo, Mikhailovsky Theatre]
  • A. wasRenamedBackTo
    Indicates that an entity, after having its name changed, was later restored to its previous or original name.
  • B. nameRestored chosen
    Indicates that an entity’s original or correct name has been reinstated after having been changed, lost, or altered.
  • C. revertedLeagueName
    Indicates that an entity’s league name has been changed back to a previous or original league name after a prior modification.
  • D. reestablishedUnderCurrentName
    Indicates that an entity previously existed under a different name and was later reestablished using its current name.
  • E. renamedDueTo
    Indicates that one entity was renamed as a consequence of another specified cause, event, or condition.
  • 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_69f34946a5208190bbd79f0fec4323bd completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6d0d46aec819091edf97324d793ac completed May 3, 2026, 4:36 a.m.
PD Predicate disambiguation batch_69f6cfe5f93c8190995c53dbbe380a32 completed May 3, 2026, 4:32 a.m.
Created at: May 1, 2026, 1:19 a.m.