Triple

T26620041
Position Surface form Disambiguated ID Type / Status
Subject Charles Gleason E668167 entity
Predicate hasNameComponentVariant P161294 FINISHED
Object Charles has variants such as Charlie or Chuck 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: Charles has variants such as Charlie or Chuck | Statement: [Charles Gleason, hasNameComponentVariant, Charles has variants such as Charlie or Chuck]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNameComponentVariant
Context triple: [Charles Gleason, hasNameComponentVariant, Charles has variants such as Charlie or Chuck]
  • A. hasNameVariantType
    Indicates that one name is a specific type or variant of another name, such as an alias, abbreviation, or alternative spelling.
  • B. nameHasVariant chosen
    Indicates that an entity’s name has an alternative or variant form.
  • C. hasVariantFamilyName
    Indicates that an entity is associated with an alternative or variant form of a family (last) name, differing from its primary recorded family name.
  • D. hasOfficialNameVariant
    Indicates that an entity has an alternative official form or version of its name.
  • E. hasComponentName
    Indicates that an entity includes or is associated with a component identified by a specific name.
  • 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_69ee9cfe16088190a3dddd68e3c7b1ea completed April 26, 2026, 11:17 p.m.
NER Named-entity recognition batch_69f70e8755a48190931eaa77946f9460 completed May 3, 2026, 8:59 a.m.
PD Predicate disambiguation batch_69f70abc00848190a1c3f495ef6c8dc6 completed May 3, 2026, 8:43 a.m.
Created at: April 27, 2026, 2:20 a.m.