Triple
T16642843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empress Xiaojing |
E404385
|
entity |
| Predicate | eraName |
P2938
|
FINISHED |
| Object | Longqing |
E373469
|
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: Longqing | Statement: [Empress Xiaojing, eraName, Longqing]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Longqing Context triple: [Empress Xiaojing, eraName, Longqing]
-
A.
Longqing
chosen
Longqing was the era name of a brief but notable period of the Ming dynasty in China, associated with the reign of the Longqing Emperor in the 16th century.
-
B.
Longqingxia
Longqingxia is a scenic gorge near Beijing, China, famous for its dramatic cliffs, reservoir, and popular boat tours through its narrow canyon.
-
C.
Heqing
Heqing was an era name used during the Northern Qi dynasty in imperial China to designate a specific reign period.
-
D.
Qinghe
Qinghe is a subdistrict in Beijing’s Haidian District, known primarily as a residential and administrative area within the city’s northwestern urban zone.
-
E.
Xingyuan
Xingyuan was the Chinese era name used during part of Emperor Dezong of Tang’s reign in the late eighth century.
- 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_69d8838a41f08190b0c3f79c47df5078 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37ad27b5481908316b4f23fb8bc32 |
completed | April 18, 2026, 12:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0084bd1b648190b6189533dcd7b9ac |
completed | May 10, 2026, 1:14 p.m. |
Created at: April 10, 2026, 5:18 a.m.