Triple
T16061073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xinyou Coup |
E389611
|
entity |
| Predicate | opponent |
P437
|
FINISHED |
| Object | Zaiyuan |
E1193735
|
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: Zaiyuan | Statement: [Xinyou Coup, opponent, Zaiyuan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zaiyuan Context triple: [Xinyou Coup, opponent, Zaiyuan]
-
A.
Zaiyuan
chosen
Zaiyuan was a late Qing dynasty Manchu prince and statesman who played a key role in court politics and was ultimately executed for his involvement in the failed Xinyou Coup of 1861.
-
B.
Jianyan
Jianyan was the reign era name marking the early rule of Emperor Gaozong during the Southern Song dynasty in China.
-
C.
Dunhua
Dunhua is a county-level city in northeastern China's Jilin Province, known for its location within the Yanbian Korean Autonomous Prefecture and its mix of Han and Korean cultural influences.
-
D.
Xingyuan
Xingyuan was the Chinese era name used during part of Emperor Dezong of Tang’s reign in the late eighth century.
-
E.
Xinzhu
Xinzhu is a city that serves as a sister city to Bielefeld, Germany, and is likely a regional urban center with cultural and economic significance.
- 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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e183795100819097be92e6d07dc5b1 |
completed | April 17, 2026, 12:48 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fff29836bc8190b35f528d3e8547be |
completed | May 10, 2026, 2:51 a.m. |
Created at: April 10, 2026, 4:57 a.m.