Triple
T4188328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2. Bundesliga |
E88368
|
entity |
| Predicate | promotionPlayoffPlaces |
P41171
|
FINISHED |
| Object | 1 promotion playoff place |
—
|
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: 1 promotion playoff place | Statement: [2. Bundesliga, promotionPlayoffPlaces, 1 promotion playoff place]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotionPlayoffPlaces Context triple: [2. Bundesliga, promotionPlayoffPlaces, 1 promotion playoff place]
-
A.
playOffPromotionPlaces
chosen
Indicates the number or set of league positions that qualify teams for participation in promotion play-off matches.
-
B.
playoffQualification
Indicates that an entity has secured a position to participate in a postseason playoff competition based on qualifying criteria.
-
C.
playoffPoints
Indicates the number of points an entity has earned or been credited with in playoff or postseason competition.
-
D.
numberOfPlayoffTeams
Indicates the total count of teams that qualify for or participate in the playoffs within a given league or season.
-
E.
hasPlayOffs
Indicates that a competition, league, or season includes a playoff stage to determine final rankings or a champion.
- 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_69aed9477e8c81908bcb862d2db55b1d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af04b009dc8190abda3f149a5b16fa |
completed | March 9, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69af01935064819096b7619f42e164dd |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:45 p.m.