Triple
T10305104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsien |
E241730
|
entity |
| Predicate | variantOf |
P4680
|
FINISHED |
| Object | Qian (surname) |
E778032
|
NE 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: Qian (surname) | Statement: [Tsien, variantOf, Qian (surname)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Qian (surname) Context triple: [Tsien, variantOf, Qian (surname)]
-
A.
Min (Chinese surname)
Min (Chinese surname) is a relatively uncommon Chinese family name with historical roots in various regions of China, including Fujian.
-
B.
Nie (Chinese surname)
Nie is a Chinese surname with historical and cultural significance, borne by various notable figures across Chinese history and modern society.
-
C.
Qian family of Haining
chosen
The Qian family of Haining is a prominent scholarly and official lineage from Haining, Zhejiang, historically known for producing influential intellectuals and statesmen in China.
-
D.
Qianyuan
Qianyuan was a historical era name used during the reign of Emperor Jing of the Western Han dynasty in ancient China.
-
E.
Qianyuan
Qianyuan was the reign era name used by Emperor Suzong during part of the Tang dynasty in China.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d381ac38808190a8ca7457c85b625b |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d309a4508190ad9de37171a64dba |
completed | April 7, 2026, 9:48 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d71d58416081909a010e905d70e934 |
completed | April 9, 2026, 3:30 a.m. |
Created at: April 6, 2026, 11:46 a.m.