Triple
T13426901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Division (Scottish football) |
E313503
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | second tier football league |
C11857
|
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: second tier football league Context triple: [First Division (Scottish football), instanceOf, second tier football league]
-
A.
third division football league
A third division football league is a professional or semi-professional competition that represents the third tier in a country's football league system, typically featuring clubs striving for promotion to higher divisions and development of emerging talent.
-
B.
second division
chosen
Second division is a conceptual class representing a secondary or lower-tier level within a hierarchical ranking or league system, typically positioned below the top division.
-
C.
regional league
A regional league is an organized sports or competitive division composed of teams or participants from a specific geographic area that compete regularly under shared rules and scheduling.
-
D.
former football league division
A former football league division is a now-defunct tier or grouping within an organized football league system that previously structured competition among clubs before being reorganized, renamed, or discontinued.
-
E.
association football league system
An association football league system is a hierarchical structure of interconnected football leagues, typically organized by promotion and relegation, that determines the competitive levels and progression of clubs within a country 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_69d806ad0c44819088833ae1ec9e9690 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:40 p.m.