Triple

T10620769
Position Surface form Disambiguated ID Type / Status
Subject Simon Skjodt Assembly Hall E250191 entity
Predicate hasPublicAddressAnnouncerBooth P5952 FINISHED
Object yes 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: yes | Statement: [Simon Skjodt Assembly Hall, hasPublicAddressAnnouncerBooth, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPublicAddressAnnouncerBooth
Context triple: [Simon Skjodt Assembly Hall, hasPublicAddressAnnouncerBooth, yes]
  • A. hasPublicAddressSystem chosen
    Indicates that an entity is equipped with or includes a public address (PA) system for broadcasting audio announcements.
  • B. hasCollectorBooth
    Indicates that an entity has an associated collector booth, typically a designated place or station where collection-related activities (such as payments, tickets, or items) are handled.
  • C. hasBroadcaster
    Indicates that an entity is associated with or transmitted by a particular broadcaster or broadcasting organization.
  • D. publiclyAnnouncedBy
    Indicates that an action, decision, or piece of information was formally communicated to the public by a specified agent or entity.
  • E. hasAddress
    Indicates that an entity is associated with a specific address or location.
  • 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_69d6aa5993448190a493b790b8f85010 completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d6df70b0288190bf6edd705632ff02 completed April 8, 2026, 11:06 p.m.
PD Predicate disambiguation batch_69d6dd7a223c8190854409d76368f3e8 completed April 8, 2026, 10:58 p.m.
Created at: April 8, 2026, 8:49 p.m.