Triple

T27936802
Position Surface form Disambiguated ID Type / Status
Subject The Cool Mikado E700634 entity
Predicate hasNarrativeOrigin P188875 FINISHED
Object stage operetta 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: stage operetta | Statement: [The Cool Mikado, hasNarrativeOrigin, stage operetta]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNarrativeOrigin
Context triple: [The Cool Mikado, hasNarrativeOrigin, stage operetta]
  • A. hasNarrative
    Indicates that one entity contains, presents, or is associated with a story or narrative about another entity or subject.
  • B. hasNarrativeContext
    Indicates that an entity is associated with, or situated within, a particular narrative or storytelling context that frames its meaning or role.
  • C. containsNarrativeOf
    Indicates that one entity includes or presents the story, account, or narrative content of another entity.
  • D. hasAbstractNarrative
    Indicates that an entity is associated with a non-literal, conceptual, or symbolic narrative rather than a concrete, straightforward account.
  • E. hasNarrativeRole
    Indicates that an entity participates in a narrative with a specific functional role (e.g., protagonist, antagonist, narrator) relative to the story.
  • F. None of above. chosen

Provenance (4 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_69ef6a5028108190a14696d9821dde49 completed April 27, 2026, 1:53 p.m.
NER Named-entity recognition batch_69fbaf18085481908c774e8f8bbb9a41 completed May 6, 2026, 9:14 p.m.
PD Predicate disambiguation batch_69fbadf1e6008190a71bbd196ba06844 completed May 6, 2026, 9:09 p.m.
PDg Predicate description generation batch_69fbaebbb7f88190b4edfd9b83550aad completed May 6, 2026, 9:12 p.m.
Created at: April 27, 2026, 7:13 p.m.