Triple

T26383958
Position Surface form Disambiguated ID Type / Status
Subject One Song Glory E663222 entity
Predicate inUniverseIssueAddressed P161705 FINISHED
Object HIV/AIDS NE NERFINISHED

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: HIV/AIDS | Statement: [One Song Glory, inUniverseIssueAddressed, HIV/AIDS]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: inUniverseIssueAddressed
Context triple: [One Song Glory, inUniverseIssueAddressed, HIV/AIDS]
  • A. inUniverseIssue
    Indicates that an issue, event, or problem occurs within the fictional universe or narrative world itself, rather than being about real-world or external production matters.
  • B. inUniverse
    Indicates that one entity exists, occurs, or is set within the fictional or conceptual universe defined by another entity.
  • C. inUniverseReference
    Indicates that one entity makes a reference to another entity that exists within the same fictional or conceptual universe.
  • D. addressesIssue
    Indicates that one entity deals with, responds to, or attempts to resolve a specific issue associated with another entity.
  • E. inUniverseUse
    Indicates that something is used or occurs within a particular fictional or conceptual universe, as opposed to in the real world or another setting.
  • 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_69ee88374adc81909868f3bab374a32f completed April 26, 2026, 9:48 p.m.
NER Named-entity recognition batch_69f6200ac60481909895c61d050b1338 completed May 2, 2026, 4:02 p.m.
PD Predicate disambiguation batch_69f61b3a8ae0819090189fbd8eb19f2f completed May 2, 2026, 3:41 p.m.
PDg Predicate description generation batch_69f61f109ef48190873bfe18638d2046 completed May 2, 2026, 3:58 p.m.
Created at: April 26, 2026, 11:21 p.m.