Triple
T23353520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yunga |
E592981
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Yunca |
—
|
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: Yunca | Statement: [Yunga, hasAlternativeName, Yunca]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yunca Context triple: [Yunga, hasAlternativeName, Yunca]
-
A.
Yunca
chosen
Yunca is an alternative name for the extinct Mochica language once spoken on Peru’s northern coast.
-
B.
Hán
Hán is the pinyin transcription of the name of the ancient Chinese State of Han, one of the major states during the Warring States period.
-
C.
Tangut
Tangut is an extinct Tibeto-Burman language once used in the Western Xia dynasty, best known today for its large and complex logographic writing system.
-
D.
Central Yi
Central Yi is a major variety of the Yi (Loloish) language cluster spoken primarily by the Yi people in parts of southwestern China.
-
E.
Hanyu
Hanyu is a Chinese given name shared by various individuals, including notable figures in fields such as acting, sports, and academia.
- 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_69e25d24d2a4819092e6ede74c2a918d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19a15d0a48190862179254c09c6d1 |
completed | April 29, 2026, 5:41 a.m. |
Created at: April 17, 2026, 5:20 p.m.