Triple
T24194172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premier League 2005–06 |
E599782
|
entity |
| Predicate | promotedFromSecondTier |
P111522
|
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: [Premier League 2005–06, promotedFromSecondTier, Sunderland A.F.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotedFromSecondTier Context triple: [Premier League 2005–06, promotedFromSecondTier, Sunderland A.F.C.]
-
A.
promotedFrom
chosen
Indicates that an entity has advanced to a new position, role, or status from a specified prior one.
-
B.
promotedToGroup2
Indicates that an entity has been advanced or elevated in status, role, or membership into a second-level group or category.
-
C.
secondTierPromotionTo
Indicates a promotion of an entity from a lower level to the second tier within a hierarchical structure.
-
D.
hasBeenPromotedBy
Indicates that one entity has received a promotion as a result of the decision or action taken by another entity.
-
E.
promotesFrom
Indicates that one entity advances or elevates another entity from a lower position, role, or status to a higher one.
- 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_69e288cdc8b88190bf2f835d3cb4ca28 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e24947948190b609a39a2b8828ad |
completed | April 29, 2026, 10:49 a.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:36 p.m.