Triple

T6627591
Position Surface form Disambiguated ID Type / Status
Subject The Curious Savage E149842 entity
Predicate typicalProductionVenue P25526 FINISHED
Object community theatre 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: community theatre | Statement: [The Curious Savage, typicalProductionVenue, community theatre]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalProductionVenue
Context triple: [The Curious Savage, typicalProductionVenue, community theatre]
  • A. typicalVenues chosen
    Indicates that the specified locations are common or standard places where the associated activity, event, or entity usually occurs or is hosted.
  • B. intendedPerformanceVenue
    Indicates the venue or location where a performance is planned or intended to take place.
  • C. 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.
  • D. typicalVenueMetroArea
    Indicates the metropolitan area where an entity is most commonly or characteristically located or hosted.
  • E. notableRecordingVenueFor
    Indicates that a venue is particularly recognized or distinguished as the place where a specific recording was made.
  • 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_69c687ee50048190aa151765bef16193 completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6c308a08881908501c862b3029321 completed March 27, 2026, 5:48 p.m.
PD Predicate disambiguation batch_69c6ad024860819084b9b535b136ede6 completed March 27, 2026, 4:14 p.m.
Created at: March 27, 2026, 1:59 p.m.