Triple

T1592688
Position Surface form Disambiguated ID Type / Status
Subject Qin dynasty E34210 entity
Predicate capital P234 FINISHED
Object Xianyang E157600 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: Xianyang | Statement: [Qin dynasty, capital, Xianyang]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Xianyang
Context triple: [Qin dynasty, capital, Xianyang]
  • A. Xianyang, China chosen
    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.
  • B. Yan'an
    Yan'an is a historic city in China's Shaanxi province that served as the Chinese Communist Party's revolutionary base and political center during the late 1930s and 1940s.
  • 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. Xinjing
    Xinjing was the capital city of the Japanese puppet state of Manchukuo in northeastern China during the 1930s and early 1940s.
  • E. Jianye
    Jianye is an ancient name for the city now known as Nanjing, a historically significant capital in several Chinese dynasties.
  • 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_69a885fdcb9c819081ce6f0b8cd477dd completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a90929b32c8190be1a4b2d7b685735 completed March 5, 2026, 4:40 a.m.
NED1 Entity disambiguation (via context triple) batch_69ad797d8c68819093fb2bcae0a08698 completed March 8, 2026, 1:28 p.m.
Created at: March 4, 2026, 7:27 p.m.