Triple
T3525194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HX |
E74521
|
entity |
| Predicate | hasPostcodeDistrict |
P961
|
FINISHED |
| Object | HX1 |
E74521
|
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: HX1 | Statement: [HX, hasPostcodeDistrict, HX1]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HX1 Context triple: [HX, hasPostcodeDistrict, HX1]
-
A.
HX
chosen
HX is a postcode area in West Yorkshire, England, covering Halifax and surrounding towns including Hebden Bridge.
-
B.
BHX
BHX is the three-letter IATA airport code for Birmingham Airport in the United Kingdom.
-
C.
HMX-1
HMX-1 is the United States Marine Corps helicopter squadron responsible for transporting the President and other VIPs, most famously operating the aircraft known as Marine One.
-
D.
H160
The H160 is a next-generation medium twin-engine helicopter developed by Airbus Helicopters, designed for versatile missions such as offshore transport, emergency medical services, and corporate aviation.
-
E.
CHX
CHX is the National Rail station code for London Charing Cross, a major central London railway terminus and transport hub.
- 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_69ad85d0c5488190a3d8e02ebd01a1aa |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc6a8d0c819094d38b9c47fb67b4 |
completed | March 8, 2026, 6:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b37e8de2648190809369c3f0b7d85d |
completed | March 13, 2026, 3:03 a.m. |
Created at: March 8, 2026, 3:19 p.m.