Triple
T14521803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HCMM |
E340669
|
entity |
| Predicate | UNLOCODECountry |
P19525
|
FINISHED |
| Object | SO |
—
|
LITERAL 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: SO | Statement: [HCMM, UNLOCODECountry, SO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UNLOCODECountry Context triple: [HCMM, UNLOCODECountry, SO]
-
A.
UNLOCODECountryCode
Indicates that an entity is associated with a specific country code as defined by the UN/LOCODE standard.
-
B.
UNLOCODE
Indicates that an entity is associated with a specific UN/LOCODE, i.e., a standardized United Nations location code identifying a particular place used in international trade and transport.
-
C.
ISOCode
Indicates that an entity is associated with a specific standardized code defined by the International Organization for Standardization (ISO).
-
D.
linkedToISO3166-2CodesOf
Indicates a relationship where an entity is associated with, or mapped to, specific ISO 3166-2 subdivision codes that represent its corresponding administrative regions.
-
E.
ISO3166-1Code
chosen
Indicates the standardized two- or three-letter country or territory code assigned under the ISO 3166-1 international standard.
- F. None of above.
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_69d822dac79c8190a84a073f3cbaced5 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69de9a72cff08190878b4bed9b0b5eb5 |
completed | April 14, 2026, 7:50 p.m. |
| PD | Predicate disambiguation | batch_69de5c518fc08190a6ce4d8be05c4c5d |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:22 a.m.