Triple

T25666164
Position Surface form Disambiguated ID Type / Status
Subject Sky Blue Soccer E643521 entity
Predicate associatedWithRebrandOf P10460 FINISHED
Object Sky Blue FC to NJ/NY Gotham FC 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: Sky Blue FC to NJ/NY Gotham FC | Statement: [Sky Blue Soccer, associatedWithRebrandOf, Sky Blue FC to NJ/NY Gotham FC]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: associatedWithRebrandOf
Context triple: [Sky Blue Soccer, associatedWithRebrandOf, Sky Blue FC to NJ/NY Gotham FC]
  • A. rebrandedReason
    Indicates the reason or motivation for which an entity underwent a rebranding.
  • B. associatedWithCityBranding
    Indicates a relationship where something is connected to, involved in, or contributes to the branding or promotional identity of a city.
  • C. relatedBrand chosen
    Indicates a relationship where one brand is associated with, connected to, or otherwise related to another brand.
  • D. rebrandedWithNetwork
    Indicates that an entity has undergone a rebranding that includes or is associated with a specific network or network-related identity.
  • E. announcedRebrandingAs
    Indicates that one entity has publicly declared it will change its name, brand, or identity to that of 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_69e77e7e45648190a068ed3faa8016ea completed April 21, 2026, 1:41 p.m.
NER Named-entity recognition batch_69fd6f9d600c8190acf495b7fc632e4b completed May 8, 2026, 5:07 a.m.
PD Predicate disambiguation batch_69fd6e98a2948190a9f78c415ad23b8c completed May 8, 2026, 5:03 a.m.
Created at: April 21, 2026, 7:04 p.m.