Triple
T3300653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HC Lev Praha |
E69322
|
entity |
| Predicate | participatedInSeason |
P14029
|
FINISHED |
| Object | 2012–13 KHL 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: 2012–13 KHL season | Statement: [HC Lev Praha, participatedInSeason, 2012–13 KHL season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: participatedInSeason Context triple: [HC Lev Praha, participatedInSeason, 2012–13 KHL season]
-
A.
playedInSeason
chosen
Indicates that an entity (such as a player or participant) took part in or was active during a specific season.
-
B.
occurredInSeason
Indicates that an event or occurrence took place during a specific season within a temporal sequence (such as a TV show season or sports season).
-
C.
isMultiSeasonParticipantOf
Indicates that an entity has participated in the related entity across multiple seasons or iterations.
-
D.
playsInSeason
Indicates that an entity participates or performs in a specific season of an ongoing series, competition, or event.
-
E.
playedInPeriod
Indicates that an entity participated or was active during a specified time period.
- 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_69ad859e529c8190a404273f53cb487d |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0a66fcc819093931fe7a6507723 |
completed | March 8, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_69ada42625308190be257f16a623a410 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.