Triple
T12564375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HK2388 |
E295428
|
entity |
| Predicate | issuerBusinessType |
P105459
|
FINISHED |
| Object | retail banking |
—
|
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: retail banking | Statement: [HK2388, issuerBusinessType, retail banking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issuerBusinessType Context triple: [HK2388, issuerBusinessType, retail banking]
-
A.
issuerCustomerType
Indicates the type or category of customer associated with or defined by the issuer.
-
B.
issuerType
Indicates the classification or category of the entity that issues something (such as a document, credential, or instrument).
-
C.
issuerOriginalBusiness
Indicates that an entity is the original business organization that issued or created another entity (such as a document, instrument, or product).
-
D.
issuerOwnsBusinessesIn
Indicates that the issuer owns one or more business entities that are located or operate within the specified place.
-
E.
originalBusinessType
Indicates the initial or primary category of business activity or industry classification associated with an entity before any subsequent changes or reclassifications.
- 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_69d6ad9cac2c81908e8a7bed82d1e21d |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d9550d84908190aea0f50055f6d92e |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95414692881909c52a1de7d224b44 |
completed | April 10, 2026, 7:48 p.m. |
| PDg | Predicate description generation | batch_69d9550af6d48190a40e349ed0424be3 |
completed | April 10, 2026, 7:52 p.m. |
Created at: April 8, 2026, 11:49 p.m.