Triple
T8827143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Czech Extraliga |
E210043
|
entity |
| Predicate | hasTeam |
P330
|
FINISHED |
| Object | Mountfield HK |
E103665
|
NE 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: Mountfield HK | Statement: [Czech Extraliga, hasTeam, Mountfield HK]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mountfield HK Context triple: [Czech Extraliga, hasTeam, Mountfield HK]
-
A.
Mountfield HK
chosen
Mountfield HK is a professional ice hockey club based in Hradec Králové, Czech Republic, competing in the country’s top-tier league.
-
B.
Mountfield a.s.
Mountfield a.s. is a Czech company best known as a major retailer of garden equipment, swimming pools, and outdoor leisure products.
-
C.
Haynrode
Haynrode is a small village in the German state of Thuringia.
-
D.
Hillman
Hillman is a residential suburb in the City of Rockingham within the Perth metropolitan region of Western Australia.
-
E.
Hillman
Hillman is a surname of English and Ashkenazic Jewish origin borne by various notable individuals across politics, labor leadership, academia, and the arts.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca8365b28081909e48e45e95dfc405 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc6034e8dc819099116d772e87569a |
completed | April 1, 2026, midnight |
| NED1 | Entity disambiguation (via context triple) | batch_69cf895a766c81908f41e369afb05023 |
completed | April 3, 2026, 9:33 a.m. |
Created at: March 30, 2026, 6:46 p.m.