Triple
T30563423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halmstad Hammers HC |
E777906
|
entity |
| Predicate | hasTrainingSessions |
P197324
|
FINISHED |
| Object | regular team practices |
—
|
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: regular team practices | Statement: [Halmstad Hammers HC, hasTrainingSessions, regular team practices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrainingSessions Context triple: [Halmstad Hammers HC, hasTrainingSessions, regular team practices]
-
A.
hasTrainingFor
Indicates that an entity has received or possesses training that prepares it for performing a specific task, role, or function.
-
B.
hasTrainingTrack
Indicates that an entity is associated with or assigned to a specific training track or program.
-
C.
hasTrainingType
Indicates that an entity is associated with or characterized by a specific type or category of training.
-
D.
hasTrainingComplex
Indicates that an entity possesses or is associated with a dedicated facility or complex used for training activities.
-
E.
hasTrained
Indicates that one entity has provided training or instruction to another entity.
- 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_69f2249ed41c8190b175170ecfd6e1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe87b609888190913b0c3f787ecdba |
completed | May 9, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69fe8731af48819092084f6f74bf052d |
completed | May 9, 2026, 1 a.m. |
| PDg | Predicate description generation | batch_69fe87b52bd4819087d6d338fe47c97c |
completed | May 9, 2026, 1:02 a.m. |
Created at: April 29, 2026, 8:21 p.m.