Triple
T33396426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kazakhstan Premier League |
E855184
|
entity |
| Predicate | usesThreePointsForWin |
P24875
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Kazakhstan Premier League, usesThreePointsForWin, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesThreePointsForWin Context triple: [Kazakhstan Premier League, usesThreePointsForWin, yes]
-
A.
pointsForWin
chosen
Indicates the number of points awarded to an entity for achieving a win in a given context or competition.
-
B.
threePointLine
Indicates the boundary line beyond which a successful field goal attempt is scored as three points instead of two.
-
C.
usedThreePointLine
Indicates that an action or play involved or was executed from beyond the three-point line.
-
D.
pointsToWinSet
Indicates the number of points a player or side must win to secure the current set.
-
E.
classWins
Indicates that a particular class has achieved victory or success in a competitive context.
- 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_69f3496e3f1c8190bcecfa82aa9d17ff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 1, 2026, 1:35 a.m.