Triple

T1736831
Position Surface form Disambiguated ID Type / Status
Subject America's Team E37937 entity
Predicate associatedWithLeagueDivisionStatus P31726 FINISHED
Object high-profile franchise 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: high-profile franchise | Statement: [America's Team, associatedWithLeagueDivisionStatus, high-profile franchise]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: associatedWithLeagueDivisionStatus
Context triple: [America's Team, associatedWithLeagueDivisionStatus, high-profile franchise]
  • A. statusInLeague
    Indicates the standing or rank an entity holds within a particular league or competitive organization.
  • B. affiliateLeague
    Indicates that one sports organization or team is formally associated with and operates under the umbrella or partnership of a particular league.
  • C. eligibleLeague
    Indicates that an entity (such as a team or player) is qualified or permitted to participate in a particular league.
  • D. associatedLeagueRuleAdoption
    Indicates that there is a connection between an entity and the specific league rule adoption that governs or influences it.
  • E. winnerLeagueDivision
    Indicates that an entity has won a specific league division in a competitive context.
  • F. None of above. chosen

Provenance (4 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_69a8861cc6ac8190ac0b2e31ccf62851 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69ab3c2559ac8190905186406fcaccb9 completed March 6, 2026, 8:42 p.m.
PD Predicate disambiguation batch_69aa61c4023c819099cbe439aefda71f completed March 6, 2026, 5:10 a.m.
PDg Predicate description generation batch_69ab3c2479148190badc616f8e2686d4 completed March 6, 2026, 8:42 p.m.
Created at: March 4, 2026, 7:30 p.m.