Triple

T13938067
Position Surface form Disambiguated ID Type / Status
Subject World Series radio broadcasts E335168 entity
Predicate localRights P111867 FINISHED
Object team flagship radio stations 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: team flagship radio stations | Statement: [World Series radio broadcasts, localRights, team flagship radio stations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: localRights
Context triple: [World Series radio broadcasts, localRights, team flagship radio stations]
  • A. typicalRegionRights
    Indicates that certain rights or permissions are characteristic or standard for a given region.
  • B. restrictedRight
    Indicates that an entity’s ability to exercise a particular right is limited, constrained, or subject to specific conditions or prohibitions.
  • C. acquiredRightsTo
    Indicates that one entity has obtained legal or contractual ownership, control, or usage rights over something previously held by another entity.
  • D. rightsRecognizedIn
    Indicates that certain rights are formally acknowledged or upheld within a specified context, such as a legal system, jurisdiction, or document.
  • E. rightsInclude
    Indicates that one set of rights encompasses, contains, or subsumes another set of rights.
  • F. None of above. chosen

Provenance (4 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_69d81c6081b88190b53e317c3370c8fe completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de2cf5cc8c8190bea74291702b2925 completed April 14, 2026, 12:03 p.m.
PD Predicate disambiguation batch_69dbc873052c8190b33ff7f7c5a4e7ee completed April 12, 2026, 4:29 p.m.
PDg Predicate description generation batch_69dcad0fc42c8190ada203febd57e851 completed April 13, 2026, 8:45 a.m.
Created at: April 9, 2026, 10:17 p.m.