Triple
T8463317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SC Dnipro-1 |
E200096
|
entity |
| Predicate | promotionToTopTier |
P69707
|
FINISHED |
| Object | 2019 |
—
|
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: 2019 | Statement: [SC Dnipro-1, promotionToTopTier, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotionToTopTier Context triple: [SC Dnipro-1, promotionToTopTier, 2019]
-
A.
promotionBetweenLevels
Indicates a change in status where an entity is advanced from one defined level or rank to a higher one.
-
B.
promotionTo
Indicates that one entity is elevated or advanced to a higher rank, position, or status relative to another entity or context.
-
C.
promotedToRankBy
Indicates that an entity was elevated to a particular rank or position through the action or decision of another entity.
-
D.
promotionOver
Indicates that one entity has been promoted to a higher rank, position, or status relative to another entity.
-
E.
promotedBackToTopFlight
chosen
Indicates that an entity has been moved back up from a lower division or level to the highest (top-flight) tier in a competitive hierarchy.
- 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_69ca83198c4c8190a337bf717d1813f5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4a39bd48190b72be7e03cff323b |
completed | March 31, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69cbd0fc634481909842c0a30077bfde |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:10 p.m.