Triple
T26925243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TJ VŽKG Ostrava |
E677759
|
entity |
| Predicate | basedInArena |
P149985
|
FINISHED |
| Object | Ostravar Aréna |
—
|
NE NERFINISHED |
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: Ostravar Aréna | Statement: [TJ VŽKG Ostrava, basedInArena, Ostravar Aréna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedInArena Context triple: [TJ VŽKG Ostrava, basedInArena, Ostravar Aréna]
-
A.
playsInArenaLocatedIn
Indicates that an entity performs or participates in events within an arena that is geographically located in a specified place.
-
B.
hostedInArenaUsedFor
Indicates that an event or activity is hosted in an arena that is (or was) used for a particular purpose or by a particular organization.
-
C.
playedInArena
Indicates that an entity (typically a performer or team) participated in an event that took place within a specific arena.
-
D.
hasPrimaryArena
chosen
Indicates that an entity is associated with its main or principal arena where it primarily hosts or performs its activities.
-
E.
associatedWithArena
Indicates a relationship in which an entity is linked or connected to a particular arena, such as by location, use, affiliation, or operation.
- 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_69eee9bdebc48190ba90a12a63e09c73 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 27, 2026, 6:09 a.m.