Triple
T26390210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Bull multi-club system |
E663390
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multi-club football ownership network |
C44487
|
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: multi-club football ownership network Context triple: [Red Bull multi-club system, instanceOf, multi-club football ownership network]
-
A.
group of football clubs
chosen
A group of football clubs is a collection of independently organized football teams associated for purposes such as competition, governance, collaboration, or shared interests.
-
B.
sports-owning family
A sports-owning family is a family whose members collectively own and control a professional sports franchise, often influencing its strategic, financial, and cultural direction across generations.
-
C.
FIFA property
A FIFA property is any event, competition, brand element, or commercial asset owned, organized, sanctioned, or otherwise controlled by FIFA, including its tournaments, trademarks, media rights, and associated intellectual property.
-
D.
football club infrastructure
The football club infrastructure encompasses all physical and organizational facilities—such as stadiums, training grounds, medical and fitness centers, youth academies, and administrative offices—required to support the club’s sporting, commercial, and community operations.
-
E.
research plot network
A research plot network is a coordinated system of standardized study sites used to collect comparable data across locations and times for analyzing ecological or experimental patterns and processes.
- 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 26, 2026, 11:25 p.m.