Triple
T476033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peregrine Sports LLC |
E9063
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | sports ownership and management company |
C671
|
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: sports ownership and management company Context triple: [Peregrine Sports LLC, instanceOf, sports ownership and management company]
-
A.
sports team owner
chosen
A sports team owner is an individual or entity that holds the legal and financial control of a professional or amateur sports franchise, overseeing its strategic direction, operations, and major business decisions.
-
B.
professional sports league
A professional sports league is an organized association of teams or athletes that schedules and governs competitive events at the highest level of play, typically offering salaries, standardized rules, and commercialized entertainment.
-
C.
Major League Soccer club
A Major League Soccer club is a professional soccer team that competes in the top-tier men’s soccer league in the United States and Canada, operating under league-wide ownership and roster regulations.
-
D.
professional baseball team
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.
-
E.
professional basketball team
A professional basketball team is an organized group of elite basketball players, coaches, and support staff that competes in officially sanctioned leagues and tournaments as a single franchise or club.
- 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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.