Triple

T25212216
Position Surface form Disambiguated ID Type / Status
Subject The Gershwin Connection E631718 entity
Predicate tributeFocus P8925 FINISHED
Object music of George and Ira Gershwin 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: music of George and Ira Gershwin | Statement: [The Gershwin Connection, tributeFocus, music of George and Ira Gershwin]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: tributeFocus
Context triple: [The Gershwin Connection, tributeFocus, music of George and Ira Gershwin]
  • A. tributeTo chosen
    Indicates that one entity is created, given, or dedicated as a mark of respect, admiration, or honor toward another entity.
  • B. tributeIn
    Indicates that one entity pays or provides tribute within, or to the authority of, a specified place or jurisdiction.
  • C. tributeFrom
    Indicates that one entity pays or provides tribute, often as a sign of submission or obligation, to another entity.
  • D. categoryFocus
    Indicates that one entity is the primary subject, theme, or focal point within the broader category defined by the other entity.
  • E. tributeSystem
    Indicates a relationship where one entity regularly provides payments, goods, or services to another as a sign of submission, allegiance, or obligation.
  • 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_69e75a8d1aa48190a4320acd3654762c completed April 21, 2026, 11:07 a.m.
NER Named-entity recognition batch_69f47b8a42a4819094f1f77087a8c271 completed May 1, 2026, 10:08 a.m.
PD Predicate disambiguation batch_69f4683472ec8190a483b3b8afe71720 completed May 1, 2026, 8:45 a.m.
Created at: April 21, 2026, 12:58 p.m.