Triple
T16709589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HC Karlovy Vary |
E406067
|
entity |
| Predicate | usesArenaSince |
P106754
|
FINISHED |
| Object | KV Arena 2009 |
—
|
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: KV Arena 2009 | Statement: [HC Karlovy Vary, usesArenaSince, KV Arena 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesArenaSince Context triple: [HC Karlovy Vary, usesArenaSince, KV Arena 2009]
-
A.
playedInArena
Indicates that an entity (typically a performer or team) participated in an event that took place within a specific arena.
-
B.
homeArenaUsed
chosen
Indicates that a particular arena serves as the primary home venue for a team or organization.
-
C.
associatedWithArena
Indicates a relationship in which an entity is linked or connected to a particular arena, such as by location, use, affiliation, or operation.
-
D.
formerArena
Indicates that an entity was previously used as an arena but no longer serves that function.
-
E.
homeArenaUntil
Indicates that a particular venue served as an entity’s home arena up to a specified time or date.
- 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_69d8838db21081909589220fd71440a4 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3865186b48190bb45a761f5cf1a83 |
completed | April 18, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69e319c379f88190ac0adf812486f598 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:20 a.m.