Triple
T27861064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yenisey Krasnoyarsk bandy club |
E704229
|
entity |
| Predicate | playsBandyOn |
P15203
|
FINISHED |
| Object | ice |
—
|
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: ice | Statement: [Yenisey Krasnoyarsk bandy club, playsBandyOn, ice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsBandyOn Context triple: [Yenisey Krasnoyarsk bandy club, playsBandyOn, ice]
-
A.
hasBandyTeam
Indicates that an entity has or is associated with a bandy team.
-
B.
playsIceHockeyIn
Indicates that an entity participates in playing ice hockey at or within a specified location or organization.
-
C.
playsOnRinkType
chosen
Indicates that an entity participates in a game or activity on a specific type of rink surface or rink configuration.
-
D.
playsForNationality
Indicates that an athlete or player represents a particular country or nationality in a sport or competition.
-
E.
playsIceHockeyCode
Indicates that one entity participates in ice hockey under the specific code, ruleset, or organizational classification represented by the other 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_69ef840f12408190b539d00d79658abf |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 27, 2026, 6:18 p.m.