Triple
T4953513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1. FC Heidenheim |
E111224
|
entity |
| Predicate | season2023_24 |
P44654
|
FINISHED |
| Object | first-ever Bundesliga season |
—
|
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: first-ever Bundesliga season | Statement: [1. FC Heidenheim, season2023_24, first-ever Bundesliga season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: season2023_24 Context triple: [1. FC Heidenheim, season2023_24, first-ever Bundesliga season]
-
A.
playsInSeason2023-24
chosen
Indicates that an entity (typically a player or team) participates in or is part of the 2023–24 season of a given competition or league.
-
B.
dstSeason
Indicates the specific season during which daylight saving time (DST) is in effect for a given context or location.
-
C.
trainingSeason
Indicates the specific season or time period during which training activities or programs take place.
-
D.
expansionSeason
Indicates the season or time period during which an expansion (such as growth, enlargement, or extension of something) takes place.
-
E.
competitionSeason
Indicates that an entity is associated with a particular competitive season or edition of a competition.
- 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_69bd4418390c8190b7e9766a2512ce55 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd71b82dd88190adfb08c3b3191fe0 |
completed | March 20, 2026, 4:11 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3aa1388190b3e0c8ee1ba1e4fa |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:31 p.m.