Triple
T12938298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eagle Football Holdings |
E309571
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multi-club football ownership group |
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: multi-club football ownership group Context triple: [Eagle Football Holdings, instanceOf, multi-club football ownership group]
-
A.
association football club
An association football club is an organized team entity that competes in the sport of soccer under a common name, management, and identity, typically participating in official leagues and tournaments.
-
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.
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.
-
D.
group of national association football teams
A group of national association football teams is a collection of officially recognized national squads that compete in organized international football competitions under shared rules or within a common tournament structure.
-
E.
association football organization
An association football organization is an entity that governs, manages, or coordinates the playing, administration, and development of soccer competitions, clubs, and related activities within a defined scope or jurisdiction.
- 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_69d7bdfa933c8190b5a27aa4a08a19b7 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:43 p.m.