Triple
T18269647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Humanitarian Exchange Language |
E437573
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | HXL |
—
|
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: HXL | Statement: [Humanitarian Exchange Language, abbreviation, HXL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HXL Context triple: [Humanitarian Exchange Language, abbreviation, HXL]
-
A.
HXL
chosen
HXL (Humanitarian Exchange Language) is a lightweight data standard designed to improve the interoperability, quality, and rapid sharing of humanitarian data across organizations and crises.
-
B.
HLX
HLX is the ICAO airline designator for Hapag-Lloyd Express, a former German low-cost carrier.
-
C.
LHX
LHX is the stock ticker symbol for L3Harris Technologies, a major American defense and aerospace technology company.
-
D.
HXX
HXX is the National Rail station code for Heathrow Central, serving Terminals 2 and 3 at London Heathrow Airport.
-
E.
HX
HX is a postcode area in West Yorkshire, England, covering Halifax and surrounding towns including Hebden Bridge.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ff7d4f88819084123ed6c9e7e5b8 |
completed | April 19, 2026, 4:14 p.m. |
Created at: April 10, 2026, 10:34 a.m.