Triple
T8594365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sian Incident |
E203505
|
entity |
| Predicate | location |
P40
|
FINISHED |
| Object | Xi'an |
E693411
|
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: Xi'an | Statement: [Sian Incident, location, Xi'an]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Xi'an Context triple: [Sian Incident, location, Xi'an]
-
A.
Xi'an
chosen
Xi'an is a major historic city in central China, famed as the eastern terminus of the Silk Road and home to the Terracotta Army of Emperor Qin Shi Huang.
-
B.
Baoji
Baoji is a major industrial and transportation hub city in western Shaanxi Province, China, known for its manufacturing base and historical sites.
-
C.
Chang'an
Chang'an was the ancient capital of several Chinese dynasties and a major political, cultural, and trade center along the Silk Road.
-
D.
Tongchuan
Tongchuan is a prefecture-level city in central Shaanxi Province, China, historically known for its coal mining industry and location on the Loess Plateau.
-
E.
Xianyang, China
Xianyang is a historic city in Shaanxi Province, China, known as the former capital of the Qin dynasty and located near the modern metropolis of Xi’an.
- 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_69ca832a7f108190b4e4f5648abf4aa2 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46c5e8888190b721e791c449b0df |
completed | March 31, 2026, 10:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cea8c9fcc48190ba20c85e226ef5f3 |
completed | April 2, 2026, 5:35 p.m. |
Created at: March 30, 2026, 6:23 p.m.