Triple
T35732928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qiqihar KHL ice hockey team |
E1032806
|
entity |
| Predicate | partOfIceHockeyStructure |
P202600
|
FINISHED |
| Object | KHL system in China |
—
|
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: KHL system in China | Statement: [Qiqihar KHL ice hockey team, partOfIceHockeyStructure, KHL system in China]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfIceHockeyStructure Context triple: [Qiqihar KHL ice hockey team, partOfIceHockeyStructure, KHL system in China]
-
A.
mainIceHockeyVenue
Indicates that a location serves as the primary venue where a team or organization regularly plays its ice hockey games.
-
B.
iceHockeyArenaCapacity
Indicates the seating capacity or maximum number of spectators that an ice hockey arena can accommodate.
-
C.
usesStandardIceRink
Indicates that the activity, event, or entity operates on or is conducted within a regulation-size, standard ice rink.
-
D.
hasIceHockeyCapacity
Indicates that an entity is capable of hosting or accommodating ice hockey activities, such as games or practices.
-
E.
homeArenaHockey
Indicates that a particular arena serves as the designated home venue for a specific hockey team.
- F. None of above. chosen
Provenance (4 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_69f76e10e59081908d81ad9ce22f40b6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a009f53a4948190aef4ede1713e1748 |
completed | May 10, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_6a009edc53d4819080b22c1074a990f3 |
completed | May 10, 2026, 3:06 p.m. |
| PDg | Predicate description generation | batch_6a009f52ef9c8190be0e8ea2e2cd484f |
completed | May 10, 2026, 3:08 p.m. |
Created at: May 3, 2026, 4:05 p.m.