Triple
T31992142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 晏 |
E816899
|
entity |
| Predicate | readingInVietnameseSinoVietnamese |
P120136
|
FINISHED |
| Object | yến |
—
|
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: yến | Statement: [晏, readingInVietnameseSinoVietnamese, yến]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: readingInVietnameseSinoVietnamese Context triple: [晏, readingInVietnameseSinoVietnamese, yến]
-
A.
hasVietnameseReading
chosen
Indicates that an entity is associated with a specific reading or pronunciation in the Vietnamese language.
-
B.
equivalentInVietnameseChuNom
Indicates that one entity is the equivalent representation of another entity in the Vietnamese Chữ Nôm writing system.
-
C.
mandarinReadingBopomofo
Indicates the Bopomofo (Zhuyin) phonetic transcription used to represent the Mandarin pronunciation of a given expression or character.
-
D.
hasMandarinReading
Indicates that an entity is associated with a specific reading or pronunciation in Mandarin Chinese.
-
E.
ChineseNameTraditional
Indicates that an entity’s name is given in traditional Chinese characters.
- 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_69f348f8002081909a3588758ba94afb |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c1bb5f248190834161b5a6ba1ece |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:13 a.m.