Triple
T27317628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xue Xiaoqing |
E689390
|
entity |
| Predicate | hasSurnameInChineseCharacters |
P37098
|
FINISHED |
| Object | 薛 |
—
|
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: 薛 | Statement: [Xue Xiaoqing, hasSurnameInChineseCharacters, 薛]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurnameInChineseCharacters Context triple: [Xue Xiaoqing, hasSurnameInChineseCharacters, 薛]
-
A.
correspondsToChineseSurname
Indicates that one entity is the Chinese surname equivalent or counterpart of another entity.
-
B.
hasCharacterWithSurname
Indicates that an entity (such as a work or story) includes at least one character whose surname matches the specified name.
-
C.
hasMultipleChineseCharacters
Indicates that the referenced item consists of more than one Chinese character.
-
D.
hasComponentSurname
chosen
Indicates that an entity’s full name includes a specified surname as one of its component parts.
-
E.
hasJapaneseSurname
Indicates that the person or entity possesses a surname that is of Japanese origin or is commonly used in Japanese naming conventions.
- 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_69ef355c53a08190a8a92e355a7ce115 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: April 27, 2026, 11:31 a.m.