Triple
T24593767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sakizaya people |
E608607
|
entity |
| Predicate | hasEthnonymInChinese |
P156685
|
FINISHED |
| Object | 撒奇萊雅族 |
—
|
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: 撒奇萊雅族 | Statement: [Sakizaya people, hasEthnonymInChinese, 撒奇萊雅族]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEthnonymInChinese Context triple: [Sakizaya people, hasEthnonymInChinese, 撒奇萊雅族]
-
A.
hasEthnonymMeaning
Indicates that one entity is the meaning or semantic interpretation of an ethnonym (a name for an ethnic group) associated with another entity.
-
B.
correspondsToChineseSurname
Indicates that one entity is the Chinese surname equivalent or counterpart of another entity.
-
C.
hasEthnonymCountry
Indicates that an ethnonym (a name for an ethnic group or people) is associated with or pertains to a specific country.
-
D.
hasEthnonymVariant
Indicates that one ethnonym is an alternative or variant form of another ethnonym referring to the same ethnic group.
-
E.
hasMeaningInChinese
Indicates that one entity (such as a word, phrase, or symbol) possesses a specific meaning or interpretation within the Chinese language.
- 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_69e2c4cf54248190af7b0c2d9ade9830 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6ca751c8190a040c10d701ecf3a |
completed | April 30, 2026, 12:48 a.m. |
| PDg | Predicate description generation | batch_69f2b8b8bc5881908df49c0b07110246 |
completed | April 30, 2026, 2:04 a.m. |
Created at: April 18, 2026, 2:30 a.m.