Triple

T38660013
Position Surface form Disambiguated ID Type / Status
Subject Bashu E940003 entity
Predicate hasTraditionalPerformance P10229 FINISHED
Object Sichuan opera 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: Sichuan opera | Statement: [Bashu, hasTraditionalPerformance, Sichuan opera]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTraditionalPerformance
Context triple: [Bashu, hasTraditionalPerformance, Sichuan opera]
  • A. hasPerformanceConvention
    Indicates that there is an agreed-upon set of rules, norms, or standards governing how a particular performance or activity should be carried out.
  • B. performanceTradition chosen
    Indicates a relationship where a performance is carried out according to a specific cultural, historical, or stylistic tradition.
  • C. hasTraditionalValue
    Indicates that something embodies, reflects, or is associated with long-established customs, norms, or cultural values.
  • D. hasLivePerformanceTradition
    Indicates that there exists an established custom or practice of performing the subject live, typically before an audience.
  • E. hasTraditionalFeatures
    Indicates that something possesses characteristics or attributes commonly associated with established traditions or customary practices.
  • 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_69f76ede49648190a48bfe47032a05a3 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_6a0075be7f54819081ab12bc1dab53bb completed May 10, 2026, 12:10 p.m.
PD Predicate disambiguation batch_6a0073a19030819098c23faa3adcb96e completed May 10, 2026, 12:01 p.m.
Created at: May 3, 2026, 4:33 p.m.