Triple
T23243783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yuan Shikai |
E581528
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Yuan |
—
|
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: Yuan | Statement: [Yuan Shikai, familyName, Yuan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yuan Context triple: [Yuan Shikai, familyName, Yuan]
-
A.
Yuan
chosen
Yuan is a common Chinese surname with historical roots and notable bearers in business, politics, and the arts.
-
B.
Chinese yuan
The Chinese yuan is the official currency of the People's Republic of China and one of the world's major reserve and trading currencies.
-
C.
RMB
RMB is the commonly used abbreviation for the Danish professional ice hockey team Rødovre Mighty Bulls.
-
D.
RMB
RMB (Rand Merchant Bank) is a leading South African corporate and investment bank known for its innovative financial solutions and advisory services across Africa and beyond.
-
E.
gold yuan
The gold yuan was a short-lived Chinese currency introduced in 1948 during the late Republican era as part of an unsuccessful attempt to curb hyperinflation.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e24606b17c81908aba1a4911c8a8ba |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f192efd44c8190b179b4d1cb71efa5 |
completed | April 29, 2026, 5:11 a.m. |
Created at: April 17, 2026, 4:10 p.m.