Triple

T28390341
Position Surface form Disambiguated ID Type / Status
Subject GV E719136 entity
Predicate hasAlternativeNicknames P149399 FINISHED
Object GVSU 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: GVSU | Statement: [GV, hasAlternativeNicknames, GVSU]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAlternativeNicknames
Context triple: [GV, hasAlternativeNicknames, GVSU]
  • A. hasNicknames chosen
    Indicates that an entity is known or referred to by one or more alternative informal names.
  • B. hasAlternativeFamilyName
    Indicates that an entity is associated with an additional or variant family name besides its primary family name.
  • C. hasNicknamedEntityType
    Indicates that an entity is associated with another entity type specifically in the role of being its nickname or informal name.
  • D. haveAlternativeTitle
    Indicates that an entity is known by one or more alternative titles or names in addition to its primary title.
  • E. alsoKnownAs
    Indicates that one entity is an alternative name, alias, or designation for another entity.
  • 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_69eff6ef211081909d31d9be5f5567e6 completed April 27, 2026, 11:53 p.m.
NER Named-entity recognition batch_69f6e6029a10819098ff21f58079e70e completed May 3, 2026, 6:06 a.m.
PD Predicate disambiguation batch_69f6e3d5e8188190b1e1c2e5d1b77031 completed May 3, 2026, 5:57 a.m.
Created at: April 28, 2026, 1:13 a.m.