Triple
T27627533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zappers |
E696248
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Fan Controlled Football team |
C28185
|
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: Fan Controlled Football team Context triple: [Zappers, instanceOf, Fan Controlled Football team]
-
A.
fan-owned organization
A fan-owned organization is an entity, such as a sports club or entertainment franchise, whose ownership and key governance decisions are collectively held and exercised by its fans or supporters rather than traditional private or corporate owners.
-
B.
World Football League team
A World Football League team is a professional American football organization that competed in the short-lived World Football League, representing a specific city or region and consisting of players, coaches, and staff participating in league games and events.
-
C.
fictional American football team
A fictional American football team is an imagined sports franchise, complete with players, coaches, branding, and history, created for use in stories, games, or other creative works.
-
D.
United Football League team
A United Football League team is a professional American football franchise that competes in the United Football League, representing a specific city or region with its own roster, coaching staff, and branding.
-
E.
American football organization
chosen
An American football organization is an entity that manages, promotes, and governs American football activities, including teams, competitions, player development, and related operations within a defined scope or region.
- 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_69ef59092c8881908114ad184248cc46 |
completed | April 27, 2026, 12:39 p.m. |
Created at: April 27, 2026, 2:19 p.m.