Triple
T15068973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Águilas de Mexicali |
E379826
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mexican Pacific League team |
C35403
|
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: Mexican Pacific League team Context triple: [Águilas de Mexicali, instanceOf, Mexican Pacific League team]
-
A.
Mexican League team
A Mexican League team is a professional baseball club based in Mexico that competes in the country’s top-tier summer league, representing a specific city or region and participating in regular-season and postseason play.
-
B.
Dominican Winter League team
A Dominican Winter League team is a professional baseball club based in the Dominican Republic that competes in the country’s winter baseball championship, typically featuring a mix of local and international players.
-
C.
independent league baseball team
An independent league baseball team is a professional baseball club that operates outside the structure and affiliations of Major League Baseball’s farm system, organizing its own player recruitment, development, and competition within an unaffiliated league.
-
D.
Federal League team
A Federal League team is a professional baseball club that competed in the short-lived Federal League, an independent major league that operated in the United States from 1914 to 1915.
-
E.
Cuban baseball team
A Cuban baseball team is an organized group of players representing a Cuban city, province, or institution in competitive baseball leagues or tournaments, reflecting the country’s strong baseball tradition and national pride.
- F. None of above. chosen
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_69d85cd7683881908d405c1b5d7b4f7f |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 3:02 a.m.