Triple
T20832120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian Bandy Super League |
E512853
|
entity |
| Predicate | usesStandardBandyRules |
P6601
|
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: [Russian Bandy Super League, usesStandardBandyRules, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesStandardBandyRules Context triple: [Russian Bandy Super League, usesStandardBandyRules, yes]
-
A.
usesAmericanRules
Indicates that the action, process, or system is conducted according to American rules or standards rather than other rule sets.
-
B.
usesLimitedOversRules
Indicates that the action or event is conducted under limited-overs rules, typically involving a fixed maximum number of overs per side.
-
C.
playedUnderRulesOf
chosen
Indicates that an activity or game was conducted in accordance with a specified set of rules or regulations.
-
D.
usesStandardIceRink
Indicates that the activity, event, or entity operates on or is conducted within a regulation-size, standard ice rink.
-
E.
hasShootoutRule
Indicates that a competition, game, or match is governed by a specific rule or set of rules for resolving ties through a shootout.
- 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_69e0b4cf62a88190bbf92351e9e57259 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c3224e788190bfc4d3dcbaa674a7 |
completed | April 21, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a1f4f48190aa9fb4ef8f8aea5a |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:42 p.m.