Triple
T6237222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chippa United F.C. |
E139505
|
entity |
| Predicate | relegatedFromTopFlight |
P34123
|
FINISHED |
| Object | 2012–13 season |
—
|
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: 2012–13 season | Statement: [Chippa United F.C., relegatedFromTopFlight, 2012–13 season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relegatedFromTopFlight Context triple: [Chippa United F.C., relegatedFromTopFlight, 2012–13 season]
-
A.
relegatedFrom
chosen
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.
-
B.
relegatedFromPremierLeague
Indicates that a football club has been demoted from the Premier League to a lower division at the end of a season.
-
C.
relegationToJ2
Indicates that a team or club is demoted from a higher football division to Japan’s J2 League.
-
D.
relegatedFromBPoolPreviousYear
Indicates that an entity was demoted or dropped from the B Pool in the previous year.
-
E.
demotedToSecondTierBy
Indicates that an entity’s status, rank, or priority has been reduced by another entity to a secondary or lower tier.
- 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_69c008b0e7ac8190808a59573ee646f3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063021258819093a9237041816638 |
completed | March 22, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69c05601de6481909d0880048fd7b49a |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:23 p.m.