Triple

T30622443
Position Surface form Disambiguated ID Type / Status
Subject Come On In the Room E779484 entity
Predicate performanceFor P6103 FINISHED
Object corporate worship 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: corporate worship | Statement: [Come On In the Room, performanceFor, corporate worship]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: performanceFor
Context triple: [Come On In the Room, performanceFor, corporate worship]
  • A. performanceAs
    Indicates that one entity serves in a particular role, character, or capacity within a performance or presentation involving another entity.
  • B. performanceWith
    Indicates a relationship where two or more entities participate together in the same performance or staged presentation.
  • C. performanceUse
    Indicates that something is used, employed, or utilized in the course of performing an action, task, or function.
  • D. performanceBasis
    Indicates that one entity’s performance is evaluated, determined, or justified on the basis of another specified factor, standard, or reference.
  • E. featuresPerformanceBy chosen
    Indicates a relationship where something (such as an event, work, or production) includes or showcases a performance given by a particular performer or group.
  • 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_69f224a3307081909a6dca8ca75dbf48 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69fd68abf52881909c5a390c362b7c59 completed May 8, 2026, 4:38 a.m.
PD Predicate disambiguation batch_69fd6812d0c88190930d8fa2d4b92490 completed May 8, 2026, 4:35 a.m.
Created at: April 29, 2026, 8:27 p.m.