Triple
T11216777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Häme University of Applied Sciences |
E265457
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | HAMK |
E911272
|
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: HAMK | Statement: [Häme University of Applied Sciences, abbreviation, HAMK]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HAMK Context triple: [Häme University of Applied Sciences, abbreviation, HAMK]
-
A.
HAMK
chosen
HAMK is a Finnish university of applied sciences offering practice-oriented higher education and research across multiple campuses in the Häme region.
-
B.
HAM
HAM is the IATA airport code for Hamburg Airport, the international airport serving the city of Hamburg, Germany.
-
C.
HAM
HAM is the standard abbreviation used for the Canadian Football League team, the Hamilton Tiger-Cats.
-
D.
HAM
HAM is the standard abbreviation used for the Hamilton Bulldogs, a Canadian junior ice hockey team based in Hamilton, Ontario.
-
E.
MHK
MHK is the post-nominal abbreviation used by elected members of the House of Keys, the lower branch of the Isle of Man's parliament.
- 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_69d6aac59460819089b9848b27f57848 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8e8eef48190932a85784ce15c86 |
completed | April 9, 2026, 5:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e4ad1c57908190a5c65ea4738722e3 |
completed | April 19, 2026, 10:23 a.m. |
Created at: April 8, 2026, 9:30 p.m.