Triple

T37665663
Position Surface form Disambiguated ID Type / Status
Subject Switch 2 E937813 entity
Predicate hasAnnouncementStatus P144449 FINISHED
Object not fully detailed publicly (as of 2024) 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: not fully detailed publicly (as of 2024) | Statement: [Switch 2, hasAnnouncementStatus, not fully detailed publicly (as of 2024)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAnnouncementStatus
Context triple: [Switch 2, hasAnnouncementStatus, not fully detailed publicly (as of 2024)]
  • A. hasAnnouncement
    Indicates that an entity issues, contains, or is associated with a specific announcement.
  • B. hasAnnouncementsSystem
    Indicates that an entity is equipped with or uses a system for creating, managing, and delivering announcements.
  • C. hasBroadcastStatus chosen
    Indicates the current broadcast-related state or condition of an item, such as whether it is scheduled, live, completed, or unavailable.
  • D. hasAnnouncers
    Indicates that one entity serves as the announcer or commentary provider for another entity, such as an event, program, or broadcast.
  • E. hasPartyAnnouncements
    Indicates that there exist announcements or notifications associated with a particular party or event.
  • 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_69f76ed6df7c8190b018e5baea716ceb completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fd82ed2a4c81908bd7797fbd2e3d08 completed May 8, 2026, 6:30 a.m.
PD Predicate disambiguation batch_69fd814cc10481908e4f8123d35a5d0c completed May 8, 2026, 6:23 a.m.
Created at: May 3, 2026, 4:18 p.m.