Triple
T27064634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xue Fei |
E685138
|
entity |
| Predicate | hasNameInChinesePinyin |
P41219
|
FINISHED |
| Object | Xue Fei |
—
|
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: Xue Fei | Statement: [Xue Fei, hasNameInChinesePinyin, Xue Fei]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameInChinesePinyin Context triple: [Xue Fei, hasNameInChinesePinyin, Xue Fei]
-
A.
hasEthnonymInChinese
Indicates that an entity has a specific ethnonym (name for an ethnic group or people) expressed in the Chinese language.
-
B.
nameInChinese
Indicates that an entity has a specific written name or label expressed in the Chinese language.
-
C.
bearerNameInPinyin
Indicates that the bearer’s name is represented in its pinyin (romanized Chinese) form.
-
D.
hasNameInKanji
Indicates that an entity is associated with a specific written form of its name in Kanji characters.
-
E.
ChinesePinyin
chosen
Indicates that one entity is the Chinese pinyin (romanized phonetic transcription) representation of another entity.
- 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_69ef14835fcc81908bd737b4267ae528 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: April 27, 2026, 8:24 a.m.