Triple
T37914356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HC ’05 Banská Bystrica |
E945772
|
entity |
| Predicate | hasCompetitiveStatus |
P83772
|
FINISHED |
| Object | professional club |
—
|
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: professional club | Statement: [HC ’05 Banská Bystrica, hasCompetitiveStatus, professional club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompetitiveStatus Context triple: [HC ’05 Banská Bystrica, hasCompetitiveStatus, professional club]
-
A.
competitiveStatus
Indicates the nature or level of competition that exists between entities, such as whether they are rivals, collaborators, or non-competitors.
-
B.
statusInCompetition
chosen
Indicates the current standing or role an entity holds within a specific competition or contest.
-
C.
hasCompetition
Indicates that one entity is in a state of rivalry or contest with another entity, typically competing for the same goal, resource, or advantage.
-
D.
isCompetitive
Indicates that one entity engages in rivalry or competition with another, typically striving to outperform or win against it.
-
E.
tieneCompetencia
Indicates that one entity has or faces competition from another 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_69f76ef2ebd88190be5229f2621070b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.