Triple

T31243462
Position Surface form Disambiguated ID Type / Status
Subject Jet (live performance recordings) E796622 entity
Predicate hasPerformanceEnvironment P44703 FINISHED
Object concert venue 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: concert venue | Statement: [Jet (live performance recordings), hasPerformanceEnvironment, concert venue]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPerformanceEnvironment
Context triple: [Jet (live performance recordings), hasPerformanceEnvironment, concert venue]
  • A. hasPerformanceContext chosen
    Indicates that an entity is associated with a specific performance-related situation, setting, or set of conditions under which it operates or is evaluated.
  • B. hasPerformanceElement
    Indicates that one entity includes, contains, or is associated with a specific performance-related component or element.
  • C. hasModernPerformance
    Indicates that an entity includes, features, or is associated with a contemporary or updated performance or execution of something (such as a work, function, or capability).
  • D. hasPerformanceProfile
    Indicates that an entity is associated with a specific performance profile that characterizes its performance attributes or behavior.
  • E. hasSoftwareEnvironment
    Indicates that an entity is associated with, or operates within, a particular software environment or configuration.
  • 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_69f224dc84d0819081f1cb6f9127e6b1 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69fd05ba6b2c81909c62b46237d10365 completed May 7, 2026, 9:35 p.m.
PD Predicate disambiguation batch_69fd03039e48819082b6e12c5453885a completed May 7, 2026, 9:24 p.m.
Created at: April 29, 2026, 9:11 p.m.