Triple
T30964143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 0857.HK |
E788903
|
entity |
| Predicate | hasRIC |
P181344
|
FINISHED |
| Object | 0857.HK |
—
|
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: 0857.HK | Statement: [0857.HK, hasRIC, 0857.HK]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRIC Context triple: [0857.HK, hasRIC, 0857.HK]
-
A.
hasRFC
Indicates that an entity is associated with, described by, or defined in a specific RFC (Request for Comments) document.
-
B.
hasNationalIdentity
Indicates that an entity possesses or is associated with a particular national identity or nationality.
-
C.
hasANC
Indicates that an entity has received or is associated with antenatal care (ANC) services.
-
D.
hasUSAN
Indicates that an entity has a specified United States Adopted Name (USAN), typically a nonproprietary name assigned to a pharmaceutical substance.
-
E.
hasRIO
Indicates that an entity is associated with, or possesses, a specific Region of Interest (RIO) in a given context.
- F. None of above. chosen
Provenance (4 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_69f224c3a6b48190951add9b7b7f0271 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
| PDg | Predicate description generation | batch_69f7688cea58819098bdfd7c80df7634 |
completed | May 3, 2026, 3:23 p.m. |
Created at: April 29, 2026, 8:54 p.m.