Triple
T19325942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1. FC Heidenheim |
E483350
|
entity |
| Predicate | promotedToBundesliga |
P49149
|
FINISHED |
| Object | 2023 |
—
|
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: 2023 | Statement: [1. FC Heidenheim, promotedToBundesliga, 2023]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotedToBundesliga Context triple: [1. FC Heidenheim, promotedToBundesliga, 2023]
-
A.
wonBundesligaWith
Indicates that one entity achieved victory in the Bundesliga while being associated with (e.g., playing for or coaching) the other entity.
-
B.
hasPromotionToTopDivisionFrom
Indicates that an entity gains promotion to the top division originating from the specified lower division or competition.
-
C.
teamManagedToPromotion
chosen
Indicates that a team successfully achieved promotion to a higher level, league, or division.
-
D.
replacedAsTopDivisionBy
Indicates that one top-level division or league has been superseded and taken over in status or role by another.
-
E.
promotionRelegation
Indicates a relationship where an entity’s status or level changes up or down within an ordered hierarchy based on performance or criteria.
- 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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e60d8bb28c81909b3a3bbb96b69b4f |
completed | April 20, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0ef66881909d489d634eee817a |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:33 p.m.