Triple
T3920794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HN |
E88951
|
entity |
| Predicate | hasRelatedCode |
P37
|
FINISHED |
| Object | HND |
E88952
|
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: HND | Statement: [HN, hasRelatedCode, HND]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HND Context triple: [HN, hasRelatedCode, HND]
-
A.
HND
chosen
HND is the three-letter ISO 3166-1 alpha-3 country code assigned to Honduras.
-
B.
HND
HND is the IATA airport code for Tokyo International Airport, commonly known as Haneda Airport, one of Japan’s busiest and primary airports serving the Tokyo metropolitan area.
-
C.
BTEC
BTEC is a vocational qualification from the UK that focuses on practical, career-oriented learning across a wide range of subjects.
-
D.
HSC
HSC is the abbreviation for the Harmonized System Committee, the international body responsible for overseeing and updating the Harmonized Commodity Description and Coding System used in global trade.
-
E.
HSC
HSC is the three-letter station code used to identify High Street Kensington Underground station on the London Underground network.
- 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_69aed955229881909e85e73ffab1d343 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeed5c28b08190b32ce81e5bd8f586 |
completed | March 9, 2026, 3:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5286c807481908a67471da777b264 |
completed | March 14, 2026, 9:20 a.m. |
Created at: March 9, 2026, 3:22 p.m.