Triple

T17630497
Position Surface form Disambiguated ID Type / Status
Subject Hitchin Town F.C. E429961 entity
Predicate hasAbbreviation P43 FINISHED
Object HTFC 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: HTFC | Statement: [Hitchin Town F.C., hasAbbreviation, HTFC]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: HTFC
Context triple: [Hitchin Town F.C., hasAbbreviation, HTFC]
  • A. HTFC chosen
    HTFC is the commonly used abbreviation for Hungerford Town Football Club, an English non-league football team based in Hungerford, Berkshire.
  • B. TFC
    TFC is a professional Major League Soccer club based in Toronto, Ontario, known for its passionate fan base and home matches at BMO Field.
  • C. TFC
    TFC is an international Filipino television network and streaming service that broadcasts a wide range of Philippine-produced shows, movies, and news to audiences worldwide.
  • D. TFC
    TFC is the stock ticker symbol for Truist Financial Corporation, a major U.S. bank holding company formed from the merger of BB&T and SunTrust.
  • E. TFC
    TFC is the common abbreviation for Toulouse FC, a professional football club based in Toulouse, France that competes in Ligue 1.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d889e37f308190a6aa0a69daff86c7 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e46dc01b1c819099e3329cfb8cb77f completed April 19, 2026, 5:53 a.m.
Created at: April 10, 2026, 5:52 a.m.