Triple

T35050983
Position Surface form Disambiguated ID Type / Status
Subject Elsweyr E1011328 entity
Predicate inUniverseRaceAssociation P190386 FINISHED
Object Khajiit 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: Khajiit | Statement: [Elsweyr, inUniverseRaceAssociation, Khajiit]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: inUniverseRaceAssociation
Context triple: [Elsweyr, inUniverseRaceAssociation, Khajiit]
  • A. inUniverseRaceOfReferent
    Indicates that the referent belongs to, or is a member of, a particular race within a specified fictional or conceptual universe.
  • B. inUniverseType
    Indicates that one entity exists within, or is categorized as belonging to, a particular fictional or conceptual universe type defined by the other entity.
  • C. inUniverseOrganization
    Indicates that an organization exists and operates within a specified fictional or narrative universe.
  • D. inUniverseAffiliationType
    Indicates the type or category of affiliation an entity has within a particular fictional or narrative universe.
  • E. inUniverseActivity
    Indicates that an activity or event occurs within the fictional universe or narrative world of a work, rather than outside it (e.g., in real life or meta-context).
  • 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_69f76dcfdda48190b1ebae5da8b54f12 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fcc4b700748190ae00b21d09c96695 completed May 7, 2026, 4:58 p.m.
PD Predicate disambiguation batch_69fcb0f9d3d881908a049475182fb039 completed May 7, 2026, 3:34 p.m.
PDg Predicate description generation batch_69fcc4b5f22c8190b8b256adbdc2570c completed May 7, 2026, 4:58 p.m.
Created at: May 3, 2026, 4:01 p.m.