Triple
T2240291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MH |
E49378
|
entity |
| Predicate | relatedCode |
P5026
|
FINISHED |
| Object | MHL |
E49379
|
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: MHL | Statement: [MH, relatedCode, MHL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MHL Context triple: [MH, relatedCode, MHL]
-
A.
MHL
chosen
MHL is the three-letter ISO 3166-1 alpha-3 country code representing the Republic of the Marshall Islands.
-
B.
MHL
MHL is the commonly used abbreviation for the International Hockey League, a professional ice hockey organization.
-
C.
HDMI
HDMI (High-Definition Multimedia Interface) is a widely used digital standard for transmitting high-definition audio and video between devices such as media players, computers, and displays over a single cable.
-
D.
D.V.I.
D.V.I. is the standard abbreviation for the District Court of the Virgin Islands, a federal court with jurisdiction over the U.S. Virgin Islands.
-
E.
MEL
MEL is the three-letter IATA airport code for Melbourne Airport, the primary international gateway serving Melbourne, Australia.
- 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_69a88aa84bdc819086df50e9c20b301e |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc0bccf688190bd10202a62fdf34e |
completed | March 7, 2026, 6:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae71bfb47881908c93333a9e808420 |
completed | March 9, 2026, 7:07 a.m. |
Created at: March 4, 2026, 7:47 p.m.