Triple
T10959002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ng |
E258916
|
entity |
| Predicate | usedInRegion |
P908
|
FINISHED |
| Object | Hong Kong |
E8492
|
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: Hong Kong | Statement: [Ng, usedInRegion, Hong Kong]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hong Kong Context triple: [Ng, usedInRegion, Hong Kong]
-
A.
Hong Kong, China
chosen
Hong Kong, China is a major global financial and trading hub and a Special Administrative Region of China located on the southern coast of the country.
-
B.
Kowloon
Kowloon is a densely populated urban area of Hong Kong known for its vibrant street life, markets, and skyline facing Victoria Harbour.
-
C.
Macau
Macau is a Special Administrative Region of China known for its blend of Portuguese and Chinese cultures and its major casino and tourism industry.
-
D.
Macau
Macau is a coastal municipality in the Brazilian state of Rio Grande do Norte, known for its salt production and fishing activities.
-
E.
Taipei–Hong Kong
Taipei–Hong Kong is a heavily traveled East Asian air route connecting Taiwan’s capital with Hong Kong, served by numerous carriers and popular for both business and tourism.
- 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_69d6aa88500c819097d7032ca578e74f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d77127b10481908ad1efafb2a338d1 |
completed | April 9, 2026, 9:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e2d6d70e90819093ced18f59785ab9 |
completed | April 18, 2026, 12:56 a.m. |
Created at: April 8, 2026, 9:23 p.m.