Triple
T15374003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chenghua Emperor |
E367619
|
entity |
| Predicate | regnalNumberInMing |
P118499
|
FINISHED |
| Object | 9 |
—
|
LITERAL 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: 9 | Statement: [Chenghua Emperor, regnalNumberInMing, 9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regnalNumberInMing Context triple: [Chenghua Emperor, regnalNumberInMing, 9]
-
A.
eraNumberInMing
Indicates that a specific era number is assigned within the historical context of the Ming dynasty.
-
B.
kangxiRadicalNumber
Indicates the specific Kangxi radical index number associated with a given Chinese character or component.
-
C.
compiledUnderDynasty
Indicates that a work or document was compiled during the reign or period of a specific dynasty.
-
D.
establishedUnderDynasty
Indicates that something (such as an institution, structure, or entity) was founded or created during the rule of a specific dynasty.
-
E.
functionInMingDynasty
Indicates that an entity held an official role, position, or function during the Ming Dynasty.
- 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_69d85a1483788190ad93c2748e8af34b |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e5d6f808190b0a4cdb35dc89e69 |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57005608190886cd01f640dfedb |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:18 a.m.