Triple
T23297039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ronglu |
E590201
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Ronglu |
—
|
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: Ronglu | Statement: [Ronglu, givenName, Ronglu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ronglu Context triple: [Ronglu, givenName, Ronglu]
-
A.
Ronglu
chosen
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.
-
B.
Ronglan
Ronglan is a village and railway stop in Levanger municipality in Trøndelag county, Norway.
-
C.
Chongde
Chongde was the era name used by Qing dynasty ruler Hong Taiji for the final years of his reign in the early 17th century.
-
D.
Muzong
Muzong is the temple name of the Longqing Emperor, a Ming dynasty ruler of China who reigned from 1567 to 1572.
-
E.
Muzong
Muzong is the temple name of the Tongzhi Emperor, a Qing dynasty ruler who reigned briefly in the late 19th century during a period of internal rebellion and external pressure on 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_69e25d1af9d88190a0b9b5e8fa608618 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f196cfc79081909966638cec48cf60 |
completed | April 29, 2026, 5:27 a.m. |
Created at: April 17, 2026, 5:03 p.m.