Triple

T11951731
Position Surface form Disambiguated ID Type / Status
Subject MLS Eastern Conference E284440 entity
Predicate hasTeam 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: [MLS Eastern Conference, hasTeam, Nashville SC]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nashville SC
Context triple: [MLS Eastern Conference, hasTeam, Nashville SC]
  • A. Nashville SC chosen
    Nashville SC is a professional soccer club based in Nashville, Tennessee, that competes in Major League Soccer.
  • B. Nashville FC
    Nashville FC is a Tennessee-based soccer club known for its regional rivalry with Chattanooga FC and its role in the growing American lower-division and professional soccer landscape.
  • C. North Carolina FC
    North Carolina FC is a professional soccer club based in the Raleigh–Durham area that competes in the USL Championship.
  • D. Memphis 901 FC
    Memphis 901 FC is a professional soccer club based in Memphis, Tennessee, competing in the USL Championship.
  • E. Chattanooga Red Wolves SC
    Chattanooga Red Wolves SC is a professional American soccer club based in Chattanooga, Tennessee, competing in 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_69d6ab2db38c8190b1f0ed6663ef8ada completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d90364c2608190a3946c9595c71164 completed April 10, 2026, 2:04 p.m.
NED1 Entity disambiguation (via context triple) batch_69f458f16f088190a0005ff0fd4f547f completed May 1, 2026, 7:40 a.m.
Created at: April 8, 2026, 9:45 p.m.