Triple
T16637223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Tigers (franchise lineage) |
E404240
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | baseball team franchise |
C386
|
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: baseball team franchise Context triple: [London Tigers (franchise lineage), instanceOf, baseball team franchise]
-
A.
professional baseball team
chosen
A professional baseball team is an organized group of elite baseball players, coaches, and staff that competes in officially sanctioned leagues and tournaments under a shared identity, brand, and management structure.
-
B.
Major League Baseball team
A Major League Baseball team is a professional sports organization that competes at the highest level of baseball in North America, consisting of players, coaches, and staff representing a specific city or region in the MLB.
-
C.
Major League Baseball entity
A Major League Baseball entity represents any organization, team, venue, event, or official construct that participates in, governs, or is formally recognized within the structure of Major League Baseball.
-
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.
Major League Baseball team era
A Major League Baseball team era represents a distinct span of seasons in a franchise’s history characterized by relatively stable rosters, management, and performance trends that define a recognizable phase of the team’s identity and success.
- 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_69d8838a41f08190b0c3f79c47df5078 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:18 a.m.