Triple

T16602339
Position Surface form Disambiguated ID Type / Status
Subject Terretektorh E403359 entity
Predicate intendedListeningMode P117078 FINISHED
Object live performance in large space 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: live performance in large space | Statement: [Terretektorh, intendedListeningMode, live performance in large space]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: intendedListeningMode
Context triple: [Terretektorh, intendedListeningMode, live performance in large space]
  • A. hasIntendedListeningMode chosen
    Indicates that an entity is associated with a specific listening configuration or mode that it is designed or intended to use.
  • B. intendedPerformanceMode
    Indicates the manner or mode in which an action, process, or performance is meant or designed to be carried out.
  • C. intendedViewerExperience
    Indicates the type or quality of experience that a piece of content is designed or expected to provide to its viewers.
  • D. playableMode
    Indicates that a particular mode, configuration, or state can be actively used or played within a system or application.
  • E. intendedTheater
    Indicates the theater or venue that an event, performance, or screening is planned or meant to take place in.
  • 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_69d883880d0c81908b5fcd454e767b60 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e35d770a048190be42180b03efba0b completed April 18, 2026, 10:31 a.m.
PD Predicate disambiguation batch_69e296aabc508190b3836a91b49113ad completed April 17, 2026, 8:23 p.m.
Created at: April 10, 2026, 5:17 a.m.