Triple
T22665521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premier League 2012–13 |
E559771
|
entity |
| Predicate | numberOfClubsRelegated |
P27337
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Premier League 2012–13, numberOfClubsRelegated, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfClubsRelegated Context triple: [Premier League 2012–13, numberOfClubsRelegated, 3]
-
A.
typicalRelegatedTeamsPerSeason
chosen
Indicates the usual or average number of teams that are relegated from a league in a single season.
-
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.
relegationFromSecondTierTo
Indicates that an entity is demoted from the second-highest competitive level or division to a specified lower tier or league.
-
D.
relegatedFromPremierLeague
Indicates that a football club has been demoted from the Premier League to a lower division at the end of a season.
-
E.
eliminatedClubInEurope
Indicates that one club has knocked another club out of a European competition.
- 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_69e2454a158c819093b8e35f5045efb6 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1781b3dbc8190a312843cf8c1bfc6 |
completed | April 29, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69ee62a6245881909506ff502da14137 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:08 p.m.