Triple
T5691316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wushe Incident |
E125432
|
entity |
| Predicate | location |
P40
|
FINISHED |
| Object | Wushe |
E132886
|
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: Wushe | Statement: [Wushe Incident, location, Wushe]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wushe Context triple: [Wushe Incident, location, Wushe]
-
A.
Wushe
chosen
Wushe is a mountainous region in central Taiwan historically inhabited by Indigenous Seediq people and known as the site of the 1930 Wushe Incident.
-
B.
Lu’an
Lu’an is a prefecture-level city in western Anhui Province, China, known for its mountainous terrain, tea production, and historical sites.
-
C.
Tealing
Tealing is a small rural village in eastern Scotland, situated in the Angus council area just north of Dundee.
-
D.
Temeswar
Temeswar (Timișoara) is a major city in western Romania known for its multicultural heritage and role in the 1989 Romanian Revolution.
-
E.
Chardzhou
Chardzhou is the former name of Turkmenabat, a major city in eastern Turkmenistan located on the Amu Darya River.
- 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_69c0082bb19c8190823a4facd3cba79b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c023e500ec8190bfda4f6a818aa5dc |
completed | March 22, 2026, 5:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c05a4baea481908b4766888fd3edf1 |
completed | March 22, 2026, 9:08 p.m. |
Created at: March 22, 2026, 3:44 p.m.