Triple

T24699549
Position Surface form Disambiguated ID Type / Status
Subject Katy E611691 entity
Predicate hasAssociatedNicknameForm P56482 FINISHED
Object Kate 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: Kate | Statement: [Katy, hasAssociatedNicknameForm, Kate]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAssociatedNicknameForm
Context triple: [Katy, hasAssociatedNicknameForm, Kate]
  • A. hasNicknameForm chosen
    Indicates that one entity is a nickname or informal variant form of another entity’s name.
  • B. hasNicknameStatus
    Indicates that an entity holds a particular status or classification specifically related to its nickname.
  • C. hasHumanFormName
    Indicates that an entity’s human form is known by a specific name.
  • D. usesNicknameInFormat
    Indicates that one entity refers to another using a nickname that follows a specific pattern or formatting convention.
  • E. hasNicknameThroughSuccessor
    Indicates that an entity has a nickname that is derived or inherited indirectly through its successor in some chain or sequence.
  • 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_69e2c4d76d148190b58ad612467149a5 completed April 17, 2026, 11:40 p.m.
NER Named-entity recognition batch_69f497bc12b881908fe3386c66252bf6 completed May 1, 2026, 12:08 p.m.
PD Predicate disambiguation batch_69f49366e8d08190adb4b71fe3a14683 completed May 1, 2026, 11:49 a.m.
Created at: April 18, 2026, 3:22 a.m.