Triple
T5286408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goldsborough, North Yorkshire |
E119629
|
entity |
| Predicate | hasPostcodeArea |
P920
|
FINISHED |
| Object | HG |
E250988
|
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: HG | Statement: [Goldsborough, North Yorkshire, hasPostcodeArea, HG]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HG Context triple: [Goldsborough, North Yorkshire, hasPostcodeArea, HG]
-
A.
HG
chosen
HG is the postcode area designation covering Harrogate and surrounding parts of North Yorkshire, England.
-
B.
GN
GN is a fast, meta-build system tool used primarily by the Chromium project to generate build files for Ninja.
-
C.
HL
HL is the vehicle registration code used on license plates for the German city of Lübeck.
-
D.
HM
HM is an abbreviation commonly used as a formal title for a reigning queen or king, standing for "Her Majesty" or "His Majesty."
-
E.
HM
HM is a prefix used for classes and APIs in Apple's HomeKit framework, which enables communication and control of smart home accessories on iOS and other Apple platforms.
- 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_69bd446de5648190b313a90bd96730d2 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd84d7de908190820c31fe6eb98dac |
completed | March 20, 2026, 5:33 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf06e98e48819091c666cf7872a7f8 |
completed | March 21, 2026, 9 p.m. |
Created at: March 20, 2026, 1:52 p.m.