Triple

T2063096
Position Surface form Disambiguated ID Type / Status
Subject New Zealand national sports teams E45835 entity
Predicate nicknameTheme P7596 FINISHED
Object use of the word "Black" in team nicknames 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: use of the word "Black" in team nicknames | Statement: [New Zealand national sports teams, nicknameTheme, use of the word "Black" in team nicknames]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: nicknameTheme
Context triple: [New Zealand national sports teams, nicknameTheme, use of the word "Black" in team nicknames]
  • A. namePunOn
    Indicates that one entity’s name is a play on, parody of, or humorous variation of another entity’s name.
  • B. localNickname
    Indicates that an entity is known by a particular nickname within a specific local or regional context.
  • C. reasonForNickname chosen
    Indicates the explanation or cause behind why a particular nickname was given to an entity.
  • D. fandomNickname
    Indicates that one entity is the nickname used by fans to refer to another entity (such as a person, group, or work).
  • E. isNickname
    Indicates that one name is an informal or alternative name commonly used to refer to the same person or entity as another 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_69a8891b38288190abd572ccad9b6928 completed March 4, 2026, 7:33 p.m.
NER Named-entity recognition batch_69abb9d3a92081909416c1d087876e99 completed March 7, 2026, 5:38 a.m.
PD Predicate disambiguation batch_69abb7aee9b48190999620176e3a6ee2 completed March 7, 2026, 5:29 a.m.
Created at: March 4, 2026, 7:40 p.m.