Triple

T4335928
Position Surface form Disambiguated ID Type / Status
Subject San Francisco 49ers–Los Angeles Rams rivalry E97461 entity
Predicate isMediaCoveredAs P36969 FINISHED
Object California NFL rivalry 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: California NFL rivalry | Statement: [San Francisco 49ers–Los Angeles Rams rivalry, isMediaCoveredAs, California NFL rivalry]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isMediaCoveredAs
Context triple: [San Francisco 49ers–Los Angeles Rams rivalry, isMediaCoveredAs, California NFL rivalry]
  • A. isCoveredBy
    Indicates that one entity is physically or conceptually overlaid, protected, or enclosed by another entity.
  • B. hasCoverType
    Indicates that one entity possesses or is associated with a specific type or category of cover.
  • C. mediaCovered chosen
    Indicates that one entity (such as a media outlet or source) has reported on, featured, or otherwise provided coverage of another entity or event.
  • D. isCoverOf
    Indicates that one entity functions as a protective or enclosing layer placed over another entity.
  • E. hasCoverFeature
    Indicates that one entity serves as a prominent or featured element on the cover of another entity (such as a publication, product, or media item).
  • 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_69b3454662a481908fbcd0bbfaa3a0a4 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b3516af43081908393fd0dad3d9382 completed March 12, 2026, 11:51 p.m.
PD Predicate disambiguation batch_69b34f4e13fc8190a42c519f37959d27 completed March 12, 2026, 11:42 p.m.
Created at: March 12, 2026, 11:14 p.m.