Triple
T31251022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhenyuan |
E796816
|
entity |
| Predicate | eraNameWrittenInChinese |
P4878
|
FINISHED |
| Object | 貞元 |
—
|
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: 貞元 | Statement: [Zhenyuan, eraNameWrittenInChinese, 貞元]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraNameWrittenInChinese Context triple: [Zhenyuan, eraNameWrittenInChinese, 貞元]
-
A.
eraNameInJapanese
Indicates the Japanese-language name used for a specific historical or calendar era.
-
B.
nameInChinese
chosen
Indicates that an entity has a specific written name or label expressed in the Chinese language.
-
C.
hasEthnonymInChinese
Indicates that an entity has a specific ethnonym (name for an ethnic group or people) expressed in the Chinese language.
-
D.
nameInManchuScriptOf
Indicates that one entity is the representation of another entity’s name written in Manchu script.
-
E.
eraNameUsedInDocuments
Indicates that a particular era name is used as a temporal reference in the specified documents.
- 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_69f224dc84d0819081f1cb6f9127e6b1 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:11 p.m.