Triple
T31265741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hong Kong residents |
E797248
|
entity |
| Predicate | haveDemonym |
P191
|
FINISHED |
| Object | Hongkonger |
—
|
NE NERFINISHED |
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: Hongkonger | Statement: [Hong Kong residents, haveDemonym, Hongkonger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveDemonym Context triple: [Hong Kong residents, haveDemonym, Hongkonger]
-
A.
hasDemonym
chosen
Indicates that one entity is the term (demonym) used to refer to the inhabitants or natives of another entity (typically a place).
-
B.
hasDemonymLanguage
Indicates that a language is used as the demonym (people’s name or adjective of nationality) for inhabitants of a particular place or group.
-
C.
relatedDemonym
Indicates that one entity is the demonym (name for residents or natives) associated with the other entity.
-
D.
usesDemonymForm
Indicates that one entity refers to another using a demonym form, i.e., a name derived from the inhabitants or nationality associated with that entity.
-
E.
administrativeDivisionOfDemonym
Indicates that a term is the demonym (name for residents) associated with a particular administrative division (such as a state, province, or region).
- 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_69f224de2bbc819081af6c32e1d857b9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:12 p.m.