Triple
T13426820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deutsche Eishockey Liga 2 |
E313500
|
entity |
| Predicate | hasHomeAndAwayGames |
P39328
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Deutsche Eishockey Liga 2, hasHomeAndAwayGames, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeAndAwayGames Context triple: [Deutsche Eishockey Liga 2, hasHomeAndAwayGames, true]
-
A.
hasHomeAndAwayFormat
chosen
Indicates that a competition, match, or series is structured with both home and away legs or fixtures between the same opponents.
-
B.
playedHomeGamesFrom
Indicates the time period during which a team or player hosted their home games at a particular venue.
-
C.
playedHomeGamesUntil
Indicates the period up to which a team or player hosted their home games at a particular venue.
-
D.
hasRegularSeasonGamesAgainst
Indicates that one team or participant plays scheduled, recurring competitive games against another during the regular season.
-
E.
hasHomeFieldEntireSeries
Indicates that one entity has home-field advantage for the entire duration of a series against another entity.
- 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_69d806ad0c44819088833ae1ec9e9690 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaed1f9208190bf5ef5b8a7ded376 |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03926188190ab3948d1f5d3941f |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:40 p.m.