Triple
T33554467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ma Xiangbo |
E859434
|
entity |
| Predicate | hasChineseNameComponent |
P196712
|
FINISHED |
| Object | Xiangbo |
—
|
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: Xiangbo | Statement: [Ma Xiangbo, hasChineseNameComponent, Xiangbo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChineseNameComponent Context triple: [Ma Xiangbo, hasChineseNameComponent, Xiangbo]
-
A.
hasChineseNameType
Indicates that an entity’s Chinese name belongs to a particular type or category (e.g., formal, short, transliterated).
-
B.
hasMultipleChineseCharacters
Indicates that the referenced item consists of more than one Chinese character.
-
C.
hasEthnonymInChinese
Indicates that an entity has a specific ethnonym (name for an ethnic group or people) expressed in the Chinese language.
-
D.
correspondsToChineseSurname
Indicates that one entity is the Chinese surname equivalent or counterpart of another entity.
-
E.
hasHangulName
Indicates that an entity is associated with a name written in the Korean Hangul script.
- 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_69f3497b2b68819093207971b5e13dc8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe629b4fa481908467c7c41b77f0c6 |
completed | May 8, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69fe61bb260c819083f9378a3a06ca47 |
completed | May 8, 2026, 10:20 p.m. |
| PDg | Predicate description generation | batch_69fe629a8d4c8190b4aa4dee39efc0a6 |
completed | May 8, 2026, 10:24 p.m. |
Created at: May 1, 2026, 1:40 a.m.