Triple
T28762390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | English First Division 1971–72 season |
E726149
|
entity |
| Predicate | tierInEnglishLeagueSystem |
P42313
|
FINISHED |
| Object | top tier |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: top tier | Statement: [English First Division 1971–72 season, tierInEnglishLeagueSystem, top tier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tierInEnglishLeagueSystem Context triple: [English First Division 1971–72 season, tierInEnglishLeagueSystem, top tier]
-
A.
tierInNationalFootball
Indicates the competitive level or division within a country's national football league system in which an entity (e.g., a club or team) participates.
-
B.
tierInLeagueSystem
chosen
Indicates the specific hierarchical level or division an entity occupies within an organized league system.
-
C.
countryLeagueSystem
Indicates that a particular league system operates within, or is associated with, a specific country.
-
D.
championLeagueLevel
Indicates the competitive tier or division of a league in which a champion or team competes.
-
E.
leagueType
Indicates the classification or category of a league within a broader organizational or competitive structure.
- F. None of above.
Provenance (3 batches)
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_69f03198be14819098fa74e48b3749bf |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:12 a.m.