Triple
T9974942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bury FC |
E196302
|
entity |
| Predicate | historicLeagueStatus |
P91391
|
FINISHED |
| Object | Football League club |
—
|
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: Football League club | Statement: [Bury FC, historicLeagueStatus, Football League club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicLeagueStatus Context triple: [Bury FC, historicLeagueStatus, Football League club]
-
A.
notableLeagueStatus
Indicates that an entity holds a distinguished or officially recognized status within a particular league or competitive organization.
-
B.
associatedLeagueStatus
Indicates that there exists a relationship specifying the league-related status or standing of an associated entity within a particular league context.
-
C.
professionalLeagueStatus
Indicates that an entity holds official recognition or classification as a professional-level league within its domain.
-
D.
parentLeagueStatus
Indicates the status or condition of a league in relation to its parent league or overarching league structure.
-
E.
footballStatusHistory
Indicates the recorded progression of statuses or conditions related to a football entity over time.
- F. None of above. chosen
Provenance (4 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_69ca82eea2b88190a0e511d21a31f386 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb849da448190b826cb8fbf2eeb89 |
completed | April 2, 2026, 12:28 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9daa808190b413a1b9a1e929e2 |
completed | April 1, 2026, 1:29 p.m. |
| PDg | Predicate description generation | batch_69cd358386f48190833c862b5b8c04b2 |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:48 p.m.