Triple

T32485742
Position Surface form Disambiguated ID Type / Status
Subject Hannah Khoury E830234 entity
Predicate isFictionalAgentOf P174893 FINISHED
Object United States government 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: United States government | Statement: [Hannah Khoury, isFictionalAgentOf, United States government]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isFictionalAgentOf
Context triple: [Hannah Khoury, isFictionalAgentOf, United States government]
  • A. hasFictionalAlterEgoOf
    Indicates that one entity is the fictional alter ego, persona, or alternate identity of another entity.
  • B. isFictionalPersonFrom
    Indicates that a fictional person originates from or is associated with a particular place or source.
  • C. allegedAgentOf
    Indicates that one entity is claimed or suspected, but not confirmed, to be the agent responsible for an action or event involving another entity.
  • D. isFictionallyCreatedBy
    Indicates that an entity is a fictional creation authored, invented, or brought into existence within a narrative by another entity.
  • E. ownedByFictionalCharacter
    Indicates that something is possessed or owned by a fictional (not real-world) character.
  • 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_69f34920aa4081908d8fb0277414b911 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6c90790788190a1ed09adc86ed22d completed May 3, 2026, 4:03 a.m.
PD Predicate disambiguation batch_69f6c3f42fbc8190a06eb1044c9e6094 completed May 3, 2026, 3:41 a.m.
PDg Predicate description generation batch_69f6c814c26c81908f5c47285129ff2a completed May 3, 2026, 3:59 a.m.
Created at: May 1, 2026, 12:58 a.m.