Triple
T35517759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1996–97 Premier League |
E1026463
|
entity |
| Predicate | promotedFromSecondTierForSeason |
P120629
|
FINISHED |
| Object | Sunderland A.F.C. |
—
|
NE NERFINISHED |
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: Sunderland A.F.C. | Statement: [1996–97 Premier League, promotedFromSecondTierForSeason, Sunderland A.F.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotedFromSecondTierForSeason Context triple: [1996–97 Premier League, promotedFromSecondTierForSeason, Sunderland A.F.C.]
-
A.
promotedFromPreviousSeason
Indicates that an entity has advanced or moved up from a lower level or division in the immediately preceding season.
-
B.
hasPromotionToTopDivisionFrom
chosen
Indicates that an entity gains promotion to the top division originating from the specified lower division or competition.
-
C.
nextSeasonPromotionTo
Indicates a promotion or advancement that an entity will receive in the following season.
-
D.
promotedFrom
Indicates that an entity has advanced to a new position, role, or status from a specified prior one.
-
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_69f76dfe78b081908e2b14cb88dd8c00 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:04 p.m.