Triple
T28283666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jianzhong Jingguo |
E713219
|
entity |
| Predicate | predecessorEraOfHuizong |
P128101
|
FINISHED |
| Object | Chongning |
—
|
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: Chongning | Statement: [Jianzhong Jingguo, predecessorEraOfHuizong, Chongning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorEraOfHuizong Context triple: [Jianzhong Jingguo, predecessorEraOfHuizong, Chongning]
-
A.
predecessorEraRuler
Indicates that one ruler directly preceded another as the ruler of a given era or period.
-
B.
establishedUnderDynasty
Indicates that something (such as an institution, structure, or entity) was founded or created during the rule of a specific dynasty.
-
C.
predecessorAsEasternRuler
Indicates that one entity previously held the position of eastern ruler before another entity assumed that same role.
-
D.
precedesEra
Indicates that one time period or era occurs entirely before another in chronological order.
-
E.
precededByEraInSameDynasty
chosen
Indicates that one era directly comes before another era within the same dynasty.
- F. None of above.
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_69efb52371d88190a1381c4e58a3b731 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 27, 2026, 11:24 p.m.