Triple
T2729734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Standard Chartered Bank (Hong Kong) |
E60281
|
entity |
| Predicate | segmentServed |
P1670
|
FINISHED |
| Object | individual customers |
—
|
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: individual customers | Statement: [Standard Chartered Bank (Hong Kong), segmentServed, individual customers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: segmentServed Context triple: [Standard Chartered Bank (Hong Kong), segmentServed, individual customers]
-
A.
sectorServed
Indicates the industry or economic sector that an entity primarily serves or targets with its activities, products, or services.
-
B.
isServedAt
Indicates that something (such as food, drink, or a service) is provided or made available at a particular place or venue.
-
C.
isServed
Indicates that one entity provides or delivers a service, product, or assistance to another entity.
-
D.
areaServed
Indicates the geographic region or jurisdiction within which a service, organization, or activity is provided or applicable.
-
E.
operatesInSegment
chosen
Indicates that an entity conducts its activities or provides its services within a specified market or operational segment.
- 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_69ab4b75cd908190b691ef0d1801acda |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdaeca6208190a586afb00747146a |
completed | March 7, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69abd82586f88190a98f60d3247fe2d3 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.