Triple

T858327
Position Surface form Disambiguated ID Type / Status
Subject Nashville E18543 entity
Predicate hasProfessionalSportsTeam P330 FINISHED
Object Nashville SC E61134 NE 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: Nashville SC | Statement: [Nashville, hasProfessionalSportsTeam, Nashville SC]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nashville SC
Context triple: [Nashville, hasProfessionalSportsTeam, Nashville SC]
  • A. Nashville SC chosen
    Nashville SC is a professional soccer club based in Nashville, Tennessee, that competes in Major League Soccer.
  • B. North Carolina FC
    North Carolina FC is a professional soccer club based in the Raleigh–Durham area that competes in the USL Championship.
  • C. St. Louis City SC
    St. Louis City SC is a professional soccer club competing in Major League Soccer and representing the city of St. Louis.
  • D. Louisville City FC
    Louisville City FC is a professional soccer club based in Louisville, Kentucky, that competes in the USL Championship, the second tier of the American soccer pyramid.
  • E. Greenville Triumph SC
    Greenville Triumph SC is a professional soccer club based in Greenville, South Carolina, that competes in the USL League One.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69a4938bdd3c8190a954a3c11844d9cf completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4ac4f740881909cb59a6c18a77af3 completed March 1, 2026, 9:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac8f62a0c481909186e09aa914a029 completed March 7, 2026, 8:49 p.m.
Created at: March 1, 2026, 7:39 p.m.