Triple
T18794686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2318.HK |
E459600
|
entity |
| Predicate | dualListedWith |
P105184
|
FINISHED |
| Object | 601318.SS |
—
|
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: 601318.SS | Statement: [2318.HK, dualListedWith, 601318.SS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dualListedWith Context triple: [2318.HK, dualListedWith, 601318.SS]
-
A.
hasDualListedStructure
chosen
Indicates that an entity operates under a dual-listed company structure, where two separate legal entities are listed on different stock exchanges but function as a single economic enterprise.
-
B.
dualLicensed
Indicates that an entity is simultaneously licensed under two distinct licenses or licensing regimes.
-
C.
listedWith
Indicates that an entity is included as an item or entry within a particular list, catalog, or collection.
-
D.
isListed
Indicates that an entity appears on or is included in a specified list, registry, or catalog.
-
E.
isListedSecurityOf
Indicates that one entity is a security (such as a stock or bond) that is officially listed and traded on the other entity, which is a financial exchange or trading venue.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a01dbb308190bbbbd5a18e26451e |
completed | April 20, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:53 a.m.