Triple
T25647548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Legion Baseball teams |
E643005
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | community-based sports organization |
C32414
|
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: community-based sports organization Context triple: [American Legion Baseball teams, instanceOf, community-based sports organization]
-
A.
amateur sports organization
chosen
An amateur sports organization is a non-professional group or governing body that coordinates, promotes, and manages recreational or competitive sports activities for participants who are not paid athletes.
-
B.
segregated sports organization
A segregated sports organization is an athletic governing body or club that separates participants, teams, or competitions along lines such as race, gender, or other social categories, enforcing or perpetuating unequal access and opportunities in sport.
-
C.
regional sports organization
A regional sports organization is an entity that governs, promotes, and coordinates athletic activities, competitions, and development programs within a specific geographic area.
-
D.
multi-sport club association
A multi-sport club association is an organized entity that oversees, coordinates, and supports multiple sports clubs or departments under a unified structure, providing shared governance, resources, and representation.
-
E.
section of multi-sport club
A section of a multi-sport club is a semi-autonomous subdivision dedicated to organizing, managing, and promoting activities, teams, and events for a specific sport within the larger club structure.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 21, 2026, 5:56 p.m.