Triple

T29545649
Position Surface form Disambiguated ID Type / Status
Subject Harry Tate E749622 entity
Predicate introducedAsNickname P48126 FINISHED
Object during World War I service LITERAL FINISHED

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: during World War I service | Statement: [Harry Tate, introducedAsNickname, during World War I service]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: introducedAsNickname
Context triple: [Harry Tate, introducedAsNickname, during World War I service]
  • A. isOfficialNicknameOf
    Indicates that one name is the formally recognized nickname or informal moniker used to refer to another entity.
  • B. usedAsNicknameSince chosen
    Indicates that one entity has been used as a nickname for another entity starting from a specified point in time.
  • C. nicknamedFor
    Indicates that one entity serves as the source, inspiration, or reason for another entity’s nickname.
  • D. hasNicknames
    Indicates that an entity is known or referred to by one or more alternative informal names.
  • E. propNickname
    Indicates that one entity is used as a nickname or informal alternative name 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_69f0bd48691081908cecad39bac591e0 completed April 28, 2026, 1:59 p.m.
NER Named-entity recognition batch_69fb6fdc7eb081908ab8475efb38c430 completed May 6, 2026, 4:44 p.m.
PD Predicate disambiguation batch_69fb5a986e588190b7a10892bd2ff44c completed May 6, 2026, 3:13 p.m.
Created at: April 28, 2026, 5:07 p.m.