Triple
T28845207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USL professional teams |
E728433
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | professional soccer club collective |
C18366
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: professional soccer club collective Context triple: [USL professional teams, instanceOf, professional soccer club collective]
-
A.
professional soccer team
chosen
A professional soccer team is an organized group of elite players, coaches, and support staff that competes in official leagues and tournaments under a shared identity, brand, and management structure.
-
B.
professional indoor soccer team
A professional indoor soccer team is an organized, officially sanctioned group of elite players who compete in structured, league-based indoor soccer competitions, typically within arenas designed for fast-paced, small-sided play.
-
C.
sports team collective
A sports team collective is a coordinated group of athletes, coaches, and supporting staff who work together under a shared identity to compete in organized sporting events and pursue common performance goals.
-
D.
sports organization collective
A sports organization collective is a coordinated group of sports entities—such as teams, clubs, leagues, or associations—that collaborate under shared governance, resources, or objectives to promote, manage, and develop athletic activities.
-
E.
professional club
A professional club is an organized association of individuals who share a common occupation or career interest, providing networking, development opportunities, and support within that field.
- F. None of above.
Provenance (1 batch)
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_69f0319e8e7c8190b37288c8845b9dbc |
completed | April 28, 2026, 4:03 a.m. |
Created at: April 28, 2026, 6:42 a.m.