Triple
T4975162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fourth Division |
E111746
|
entity |
| Predicate | relegationIntroduced |
P60736
|
FINISHED |
| Object | 1987 |
—
|
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: 1987 | Statement: [Fourth Division, relegationIntroduced, 1987]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relegationIntroduced Context triple: [Fourth Division, relegationIntroduced, 1987]
-
A.
relegationSystem
Indicates a system in which entities are moved to a lower tier or level based on their performance or ranking within a structured hierarchy.
-
B.
relegatedFrom
Indicates that an entity has been demoted, downgraded, or moved from a higher status, level, or position to a lower one, typically as a result of performance or evaluation.
-
C.
demotedToSecondTierBy
Indicates that an entity’s status, rank, or priority has been reduced by another entity to a secondary or lower tier.
-
D.
relegatedFromBPoolPreviousYear
Indicates that an entity was demoted or dropped from the B Pool in the previous year.
-
E.
relegatedFromPremierLeague
Indicates that a football club has been demoted from the Premier League to a lower division at the end of a season.
- 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_69bd441a0eb481908050fa4273b19eae |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd730a7590819088ab8d49c5c88c2f |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd7146e6e881908a55ab2756b631f6 |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd73089f548190834103366e24ab40 |
completed | March 20, 2026, 4:17 p.m. |
Created at: March 20, 2026, 1:33 p.m.