Triple
T21943046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sze Yup region |
E541868
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Siyi |
—
|
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: Siyi | Statement: [Sze Yup region, hasAlternativeName, Siyi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Siyi Context triple: [Sze Yup region, hasAlternativeName, Siyi]
-
A.
Enlai
Enlai is the given name of Zhou Enlai, the prominent first Premier of the People's Republic of China and a key figure in Chinese Communist history.
-
B.
Siyi Yue
chosen
Siyi Yue is a regional variety of Yue Chinese spoken primarily in the Siyi (Four Counties) area of Guangdong, China.
-
C.
Taizi
Taizi is the traditional Chinese title for the designated heir apparent to the imperial throne.
-
D.
Tianzi
Tianzi is the traditional Chinese title meaning "Son of Heaven," used to denote the supreme ruler and divinely sanctioned sovereign of imperial China.
-
E.
Consort Yi
Consort Yi was a royal consort title in the Chinese imperial court, typically granted to a high-ranking concubine favored by the emperor.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0c47e2e5c81909a7f74ce3de50911 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1242515ec8190b015bf8c7b13be85 |
completed | April 28, 2026, 9:18 p.m. |
Created at: April 16, 2026, 7:56 p.m.