Triple
T9289936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SEHK:9988 |
E223490
|
entity |
| Predicate | exchangeCode |
P15701
|
FINISHED |
| Object | SEHK |
E223490
|
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: SEHK | Statement: [SEHK:9988, exchangeCode, SEHK]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SEHK Context triple: [SEHK:9988, exchangeCode, SEHK]
-
A.
HKE
HKE is the ICAO airline designator for HK Express, a low-cost carrier based in Hong Kong.
-
B.
SEHK:9988
chosen
SEHK:9988 is the stock ticker for Alibaba Group’s shares listed on the Hong Kong Stock Exchange, representing one of China’s largest e-commerce and technology conglomerates.
-
C.
HK
HK is a renowned German defense manufacturer best known for designing and producing small arms such as pistols, rifles, and submachine guns used by military and law enforcement worldwide.
-
D.
HK
HK is the vehicle registration code used for the Czech city of Hradec Králové.
-
E.
HK
HK is the vehicle registration code used on license plates for vehicles registered in Ahlden, a municipality in Lower Saxony, Germany.
- 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_69ca8422ddf881908a3f8f876c9f53aa |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd08643a848190a8b5be1ccc0b2ef6 |
completed | April 1, 2026, 11:58 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d0b22ff5d881909ed5ac15ad8cbbb6 |
completed | April 4, 2026, 6:39 a.m. |
Created at: March 30, 2026, 7:35 p.m.