Triple

T5456077
Position Surface form Disambiguated ID Type / Status
Subject Théâtre Feydeau E122480 entity
Predicate hasWorkPerformed P12366 FINISHED
Object operas by Luigi Cherubini 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: operas by Luigi Cherubini | Statement: [Théâtre Feydeau, hasWorkPerformed, operas by Luigi Cherubini]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasWorkPerformed
Context triple: [Théâtre Feydeau, hasWorkPerformed, operas by Luigi Cherubini]
  • A. hasWorkOn
    Indicates that one entity is associated with, contributes to, or performs work on another entity (such as a project, task, or artifact).
  • B. hasWorkBy chosen
    Indicates that one entity (such as a collection, exhibition, or publication) includes or contains creative works produced by another entity (such as an artist, author, or creator).
  • C. hasWorkCount
    Indicates the number of works (such as items, creations, or outputs) associated with a given entity.
  • D. hasWorkPeriod
    Indicates that an entity is associated with a specific span of time during which it performs or is engaged in some work or activity.
  • E. hasSubsequentWork
    Indicates that one work is followed by another work that continues, succeeds, or builds upon it in sequence.
  • 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_69bd46424248819085282ddf50a565f3 completed March 20, 2026, 1:06 p.m.
NER Named-entity recognition batch_69bd927c946c8190aef40679199fede3 completed March 20, 2026, 6:31 p.m.
PD Predicate disambiguation batch_69bd91a0d96c8190bd1299edbf764bbb completed March 20, 2026, 6:27 p.m.
Created at: March 20, 2026, 2:08 p.m.