Triple
T28394477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Federation of Football History & Statistics |
E719245
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | sports statistics organization |
C42068
|
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 statistics organization Context triple: [International Federation of Football History & Statistics, instanceOf, sports statistics organization]
-
A.
sports organization collective
A sports organization collective is a coordinated group of sports entities—such as teams, clubs, leagues, or associations—that collaborate under shared governance, resources, or objectives to promote, manage, and develop athletic activities.
-
B.
sports statistics website
A sports statistics website is an online platform that collects, analyzes, and presents detailed data, metrics, and historical records about teams, players, and games across various sports.
-
C.
sports statistics body
chosen
A sports statistics body is an organization responsible for collecting, validating, analyzing, and publishing official quantitative data and records related to sports competitions, teams, and athletes.
-
D.
sports statistics topic
A sports statistics topic is a focused subject area that explores quantitative data, metrics, and analytical methods used to evaluate performance, strategy, and outcomes in athletic competitions.
-
E.
regional sports organization
A regional sports organization is an entity that governs, promotes, and coordinates athletic activities, competitions, and development programs within a specific geographic area.
- 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_69eff6efd1b08190ae3cefd4f11388a2 |
completed | April 27, 2026, 11:53 p.m. |
Created at: April 28, 2026, 1:16 a.m.