Triple
T21871188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Accrington Stanley F.C. |
E540004
|
entity |
| Predicate | competitionTierHistory |
P43092
|
FINISHED |
| Object | non-league football |
—
|
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: non-league football | Statement: [Accrington Stanley F.C., competitionTierHistory, non-league football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitionTierHistory Context triple: [Accrington Stanley F.C., competitionTierHistory, non-league football]
-
A.
competitionHierarchyLevel
chosen
Indicates the relative rank or tier of a competition within an overall competitive structure or hierarchy.
-
B.
historicalTopCompetition
Indicates that an entity has participated in or been associated with the highest-level or most prestigious competition within a historical context.
-
C.
rankHistory
Indicates the historical sequence of ranks or positions an entity has held over time.
-
D.
divisionOrConferenceHistory
Indicates the historical record of which divisions or conferences an entity has belonged to over time.
-
E.
hasCompetitionHistory
Indicates that an entity has a recorded history of participation in competitions or competitive events.
- 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_69e0c478f59081909d54302b57fc1ce3 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0f33509d08190b33775abb84d5255 |
completed | April 28, 2026, 5:49 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:57 p.m.