Triple
T27353796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European community in Hong Kong |
E685628
|
entity |
| Predicate | activeInSector |
P167775
|
FINISHED |
| Object | international business |
—
|
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: international business | Statement: [European community in Hong Kong, activeInSector, international business]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activeInSector Context triple: [European community in Hong Kong, activeInSector, international business]
-
A.
activeInTerritory
Indicates that an entity conducts operations, activities, or maintains a presence within a specified geographic territory.
-
B.
activeInBand
Indicates that an entity is a current member performing or participating in the activities of a specific band.
-
C.
activeAs
Indicates that an entity is currently functioning or serving in a particular role, capacity, or status.
-
D.
activeAt
Indicates that an entity is functioning, valid, or in effect during a specified time or at a particular location or context.
-
E.
activeWith
Indicates that an entity is currently engaged in or functioning together with another specified entity.
- 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_69ef14887c288190931b8431fdbf53c4 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f66cf092c881908d7034c9c2bc61d5 |
completed | May 2, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66c59de9881909ebbb7b0ae7ab495 |
completed | May 2, 2026, 9:27 p.m. |
Created at: April 27, 2026, 11:50 a.m.