Triple

T18006156
Position Surface form Disambiguated ID Type / Status
Subject Longchang E430751 entity
Predicate follows P134 FINISHED
Object Tianbao 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: Tianbao | Statement: [Longchang, follows, Tianbao]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tianbao
Context triple: [Longchang, follows, Tianbao]
  • A. Tianbao chosen
    Tianbao was the reign era of Emperor Xuanzong of the Tang dynasty, marking a period of cultural flourishing that ended with the outbreak of the An Lushan Rebellion.
  • B. Tianbao
    Tianbao was an era name used during the Northern Qi dynasty in imperial China to designate a specific reign period.
  • C. Sanbao
    Sanbao, better known in the West as Zheng He, was a famed 15th-century Chinese admiral and explorer who led the Ming dynasty’s great maritime expeditions across the Indian Ocean.
  • D. Qibao
    Qibao is an ancient water town and popular tourist area in Shanghai, known for its historic streets, canals, and traditional architecture.
  • E. Xiantong
    Xiantong was the reign era name used by Emperor Xizong during a late period of the Tang dynasty in China.
  • 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_69d8b904530081908bf341d842464856 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4b51c7da48190ab70775a672e2d5f completed April 19, 2026, 10:57 a.m.
Created at: April 10, 2026, 10:24 a.m.