Triple
T724277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SpVgg Greuther Fürth |
E14688
|
entity |
| Predicate | promotionToBundesliga |
P8176
|
FINISHED |
| Object | 2012 |
—
|
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 | Statement: [SpVgg Greuther Fürth, promotionToBundesliga, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotionToBundesliga Context triple: [SpVgg Greuther Fürth, promotionToBundesliga, 2012]
-
A.
promotionTo
chosen
Indicates that one entity is elevated or advanced to a higher rank, position, or status relative to another entity or context.
-
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.
hasPromotionRelegation
Indicates that there is a system in which entities can move up (promotion) or down (relegation) between hierarchical levels based on defined criteria or performance.
-
D.
returnedToPremierLeague
Indicates that an entity (typically a football club) has rejoined the Premier League after a period of absence.
-
E.
promotionBetween
Indicates a relationship where one entity advances or elevates another entity’s status, rank, or visibility relative to a previous state.
- 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_69a4934c753c81909b309027e48b9b3a |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a5a6ab508190b70a05a9d77829a5 |
completed | March 1, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f700cc81908c6de3eedf68433c |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.