Triple
T10054023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harmonized System |
E208817
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | HS |
E208817
|
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: HS | Statement: [Harmonized System, shortName, HS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HS Context triple: [Harmonized System, shortName, HS]
-
A.
HS
chosen
HS is an internationally standardized system of names and numbers used to classify traded products for customs and statistical purposes.
-
B.
HS
HS is the postcode area covering the Outer Hebrides (Western Isles) of Scotland.
-
C.
SHS
SHS is the abbreviation commonly used for the Florida State Highway System, the network of state-maintained roads in Florida.
-
D.
SHS
SHS is the commonly used abbreviation for the Shanghai Sharks, a professional basketball team based in Shanghai, China.
-
E.
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.
- 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_69ca836094408190a36a1ea7e9a86fcd |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcfab39408190ac728fe156eed658 |
completed | April 2, 2026, 2:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d282a3d3148190908f02a9588b700e |
completed | April 5, 2026, 3:41 p.m. |
Created at: March 30, 2026, 8:57 p.m.