Triple

T29930617
Position Surface form Disambiguated ID Type / Status
Subject Love-In E760203 entity
Predicate recordedLiveAt P37189 FINISHED
Object Fillmore Auditorium, San Francisco NE NERFINISHED

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: Fillmore Auditorium, San Francisco | Statement: [Love-In, recordedLiveAt, Fillmore Auditorium, San Francisco]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: recordedLiveAt
Context triple: [Love-In, recordedLiveAt, Fillmore Auditorium, San Francisco]
  • A. recordedAsLive chosen
    Indicates that an audio or video performance was captured in real time before an audience or in a live setting, rather than produced or edited in a studio environment.
  • B. notableLiveRecording
    Indicates that there exists a particularly significant or well-known live recording associated with the subject.
  • C. originallyRecordedAt
    Indicates that an audio or video work was first captured or produced at a specific location or venue.
  • D. laterRecordedAt
    Indicates that an event, action, or piece of information was recorded at a time later than another referenced recording time.
  • E. recordedDuringTourFor
    Indicates that a recording was made in the context of, or as part of, a specific tour or series of performances.
  • 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_69f224631674819080c8d089674f9f4f completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_69f7b2f3a104819098ddd8909eaf596c completed May 3, 2026, 8:41 p.m.
PD Predicate disambiguation batch_69f7b1b8a9fc8190a1279e67a2d12707 completed May 3, 2026, 8:36 p.m.
Created at: April 29, 2026, 6:17 p.m.