Triple
T9667927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haojing |
E233751
|
entity |
| Predicate | succeededBy |
P78
|
FINISHED |
| Object | Luoyi |
E237343
|
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: Luoyi | Statement: [Haojing, succeededBy, Luoyi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Luoyi Context triple: [Haojing, succeededBy, Luoyi]
-
A.
Luoyi
chosen
Luoyi was an ancient Chinese city that served as a major political and cultural center of the Zhou dynasty.
-
B.
Yuanhong
Yuanhong is a Chinese given name that appears in the full name of the historical figure Li Yuanhong.
-
C.
Ronglu
Ronglu was a high-ranking Qing dynasty general and statesman who played a key role in military and political affairs during the late imperial period, including the Boxer Rebellion.
-
D.
Heqing
Heqing was an era name used during the Northern Qi dynasty in imperial China to designate a specific reign period.
-
E.
Changyi
Changyi is a county-level coastal city in northeastern Shandong Province, China, known for its manufacturing industries and location on the Bohai Sea.
- 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_69ca848d3b6c8190ae98ea554dea58df |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c3c06e4819080c1b8e66faa482f |
completed | April 1, 2026, 10:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d190f691c8819093fe133bdbe1c9d1 |
completed | April 4, 2026, 10:30 p.m. |
Created at: March 30, 2026, 8:15 p.m.