Triple
T14374524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 0992.HK |
E356438
|
entity |
| Predicate | issuerMajorMarket |
P4848
|
FINISHED |
| Object | global |
—
|
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: global | Statement: [0992.HK, issuerMajorMarket, global]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issuerMajorMarket Context triple: [0992.HK, issuerMajorMarket, global]
-
A.
hasMajorMarket
chosen
Indicates that an entity has a primary or most significant market in a specified location or segment.
-
B.
issuerMainPlatform
Indicates that an entity serves as the primary platform or main environment through which an issuer operates, offers, or manages its services or instruments.
-
C.
issuerOperatesIn
Indicates that an issuing entity conducts business activities or has operational presence within a specified geographic area or jurisdiction.
-
D.
isPrimarySecuritiesMarketOf
Indicates that a market serves as the main or principal venue where a particular entity’s securities are initially issued, listed, or predominantly traded.
-
E.
isMajorTradingCurrencyIn
Indicates that a currency is one of the primary or most significant currencies used for trade within a specified market or region.
- 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_69d8279163a081908aec45c0e3f1e02f |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de9007184c8190aebb003cb6548cc8 |
completed | April 14, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69de2a9cb3e081909f6b33fdd939bb9e |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:16 a.m.