Triple
T20170502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hezhe |
E491944
|
entity |
| Predicate | officialClassificationInChina |
P63019
|
FINISHED |
| Object | minority nationality |
—
|
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: minority nationality | Statement: [Hezhe, officialClassificationInChina, minority nationality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialClassificationInChina Context triple: [Hezhe, officialClassificationInChina, minority nationality]
-
A.
legalStatusInChina
Indicates the legal status or standing that an entity holds under the laws and regulations of China.
-
B.
roleInChina
Indicates that one entity holds or performs a specific role, position, or function within the context of China.
-
C.
ethnicStatusInChina
chosen
Indicates the ethnic classification or status that an entity holds within the sociopolitical context of China.
-
D.
ChineseDesignation
Indicates that one entity serves as the Chinese-language name, title, or designation for another entity.
-
E.
isOneOfChinaFourMunicipalities
Indicates that the subject is one of the four directly administered municipalities of China (Beijing, Shanghai, Tianjin, or Chongqing).
- 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_69da6266c6888190bc1a3ecf24814d34 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e66847ed9481908e6b23b399fa7005 |
completed | April 20, 2026, 5:54 p.m. |
| PD | Predicate disambiguation | batch_69e55b0c11cc8190836d1eee5945f000 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:35 p.m.