Triple
T18867951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MHL |
E461488
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | MHL |
—
|
NE NERFINISHED |
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: MHL | Statement: [MHL, shortName, MHL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MHL Context triple: [MHL, shortName, MHL]
-
A.
MHL
MHL is the commonly used abbreviation for the International Hockey League, a professional ice hockey organization.
-
B.
MHL
MHL is an abbreviation that can refer to various entities, most commonly the Mobile High-Definition Link technology standard for transmitting audio and video from mobile devices to displays.
-
C.
MHL
MHL is the abbreviation for Musikhochschule Lübeck, a renowned German university-level institution specializing in music education and performance.
-
D.
MHL
The MHL is Russia’s top junior ice hockey league, serving as a key development system for young players aiming to reach professional levels such as the KHL.
-
E.
MHL
MHL is the three-letter ISO 3166-1 alpha-3 country code representing the Republic of the Marshall Islands.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide. chosen
Provenance (2 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_69d8dcfb7b9c8190854e7b171b98ea2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c2a6d1d081909b6dab2a5166a317 |
completed | April 20, 2026, 6:07 a.m. |
Created at: April 10, 2026, 11:57 a.m.