Triple

T23039363
Position Surface form Disambiguated ID Type / Status
Subject Levitt Shell Memphis E573692 entity
Predicate usesVenueFor P112843 FINISHED
Object live music performances 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 music performances | Statement: [Levitt Shell Memphis, usesVenueFor, live music performances]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesVenueFor
Context triple: [Levitt Shell Memphis, usesVenueFor, live music performances]
  • A. usesVenues
    Indicates that one entity makes use of or operates within specific venues or locations to carry out its activities or services.
  • B. usualVenueSince
    Indicates that a particular venue has been the regular or customary location for something (e.g., an event or activity) starting from a specified point in time.
  • C. homeVenueAlsoUsedBy
    Indicates that the venue serving as a home location for one entity is also used as a venue by another entity.
  • D. hostVenueInstanceOf
    Indicates that a specific host venue is an instance or concrete realization of a more general venue type or category.
  • E. hasVenueFor chosen
    Indicates that one entity provides or serves as the location or setting where an event, activity, or function takes place for another entity.
  • 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_69e245b911188190bc3d96326c847969 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f185121da0819095b523d7d2c923ab completed April 29, 2026, 4:12 a.m.
PD Predicate disambiguation batch_69ef89d5f71881908b9f9d0c8aab278c completed April 27, 2026, 4:07 p.m.
Created at: April 17, 2026, 3:53 p.m.