Triple
T21192248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Home Location Register |
E522240
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | HLR |
—
|
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: HLR | Statement: [Home Location Register, abbreviation, HLR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HLR Context triple: [Home Location Register, abbreviation, HLR]
-
A.
HLR
chosen
HLR (Home Location Register) is a central database in mobile networks that stores and manages subscriber information, authentication data, and location details for GSM users.
-
B.
HLR
HLR is the FAA location identifier for Hood Army Airfield, a U.S. Army aviation facility.
-
C.
VLR
VLR is the abbreviation for the Virginia Landmarks Register, the Commonwealth of Virginia’s official list of historically significant properties and districts.
-
D.
VLR
VLR (Visitor Location Register) is a key mobile network database that temporarily stores subscriber information and location details for users currently roaming within a specific area.
-
E.
HLU
HLU is the National Rail station code for Helensburgh Upper railway station in Argyll and Bute, Scotland.
- 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73338dbe881908360dedad65c964b |
completed | April 21, 2026, 8:20 a.m. |
Created at: April 16, 2026, 3:07 p.m.