Triple
T6633865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KHL playoffs |
E150394
|
entity |
| Predicate | usesShootout |
P3768
|
FINISHED |
| Object | false in playoffs |
—
|
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: false in playoffs | Statement: [KHL playoffs, usesShootout, false in playoffs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesShootout Context triple: [KHL playoffs, usesShootout, false in playoffs]
-
A.
hasShootoutInLeague
Indicates that a league match involved a shootout (e.g., penalty or tiebreak shootout) as part of its outcome or progression.
-
B.
shootoutUsedInRegularSeason
chosen
Indicates that a shootout tiebreaker format was employed during regular-season games.
-
C.
hasTopTenShootout
Indicates that an entity is involved in or associated with a top ten shootout event, typically a competitive session determining the ten fastest or best performers.
-
D.
numberOfSuperShooters
Indicates the count of entities that qualify as "super shooters" within a given context or group.
-
E.
shotType
Indicates the specific kind or category of shot used or taken in a given context (e.g., in film, photography, or sports).
- 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_69c687f0ceb08190bf40807bfc605fa5 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6c308a08881908501c862b3029321 |
completed | March 27, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69c6ad024860819084b9b535b136ede6 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:59 p.m.