Triple
T35949636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hvidovre IF youth |
E1039684
|
entity |
| Predicate | trainingFacilitiesUsedBy |
P175813
|
FINISHED |
| Object | Hvidovre IF youth teams |
—
|
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: Hvidovre IF youth teams | Statement: [Hvidovre IF youth, trainingFacilitiesUsedBy, Hvidovre IF youth teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trainingFacilitiesUsedBy Context triple: [Hvidovre IF youth, trainingFacilitiesUsedBy, Hvidovre IF youth teams]
-
A.
trainingFacilityUsed
chosen
Indicates that a particular training facility is utilized or employed for conducting training activities or programs.
-
B.
trainingStations
Indicates a relationship where certain locations or facilities serve as designated sites for training activities or instruction.
-
C.
trainingFacilityLocation
Indicates the place or site where a training facility is situated or operates.
-
D.
trainingLocationType
Indicates the type or category of place where a training activity occurs.
-
E.
trainingClub
Indicates that one entity serves as a club or organization where the other entity receives training.
- 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_69f76e25ea488190b7cee970b3e70382 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.