Triple
T30046124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jianxing |
E763457
|
entity |
| Predicate | usedForPartOfReignOf |
P180720
|
FINISHED |
| Object | Liu Shan |
—
|
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: Liu Shan | Statement: [Jianxing, usedForPartOfReignOf, Liu Shan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForPartOfReignOf Context triple: [Jianxing, usedForPartOfReignOf, Liu Shan]
-
A.
issuedDuringReignOf
Indicates that something (such as a document, decree, or coin) was formally issued while a particular ruler or authority was in power.
-
B.
reusedDuringReignOf
Indicates that something previously existing was used again or repurposed during the period when a particular ruler or authority was in power.
-
C.
activeInReignOf
Indicates that an entity was active or operational during the time period corresponding to a specific ruler’s reign.
-
D.
appearedDuringReignOf
Indicates that one entity came into existence, became active, or was first observed while another entity (typically a ruler or regime) was in power.
-
E.
builtDuringReignOf
Indicates that something was constructed while a particular ruler or authority was in power.
- F. None of above. chosen
Provenance (4 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_69f22470a89c8190be7273297c0e0d19 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
| PDg | Predicate description generation | batch_69f74c6fa6548190b03935f65429a24e |
completed | May 3, 2026, 1:23 p.m. |
Created at: April 29, 2026, 6:54 p.m.