Triple
T27775653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azadegan League clubs |
E699177
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | association football club collection |
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: association football club collection Context triple: [Azadegan League clubs, instanceOf, association football club collection]
-
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.
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.
-
C.
association football match collection
A collection of association football matches is an organized set of individual games grouped for a specific purpose, such as a season, tournament, or analytical dataset.
-
D.
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.
-
E.
association football player list
A structured compilation of association football players, typically organized by criteria such as team, league, nationality, position, or era, for reference or statistical purposes.
- 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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
Created at: April 27, 2026, 5:05 p.m.