Triple
T27916333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2008–09 KHL season |
E706083
|
entity |
| Predicate | regulationWinPoints |
P24875
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [2008–09 KHL season, regulationWinPoints, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulationWinPoints Context triple: [2008–09 KHL season, regulationWinPoints, 3]
-
A.
pointsForRegulationLoss
Indicates the number of points awarded to a team or player specifically for losing a game in regulation time.
-
B.
pointsForWin
chosen
Indicates the number of points awarded to an entity for achieving a win in a given context or competition.
-
C.
winnerPoints
Indicates the number of points earned by the winning participant or entity in a competition or event.
-
D.
pointsAwarded
Indicates that a specified number of points has been granted to an entity as a result of some action or event.
-
E.
regulatingRules
Indicates that one entity establishes or enforces rules or standards that govern or control the behavior, operation, or conditions of 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_69ef96b6cc808190aab19fb18b235f4b |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 27, 2026, 6:53 p.m.