Triple
T1603638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Han dynasty |
E34448
|
entity |
| Predicate | eraNameSystem |
P1217
|
FINISHED |
| Object | formalized use of reign era names |
—
|
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: formalized use of reign era names | Statement: [Han dynasty, eraNameSystem, formalized use of reign era names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraNameSystem Context triple: [Han dynasty, eraNameSystem, formalized use of reign era names]
-
A.
eraName
Indicates the named historical or chronological era associated with an entity or time period.
-
B.
usesNamingSystem
chosen
Indicates that one entity adopts or applies a particular naming system or convention to identify or label other entities.
-
C.
registryName
Indicates that an entity is identified or labeled by a specific name within a registry or registration system.
-
D.
regionNamedAfter
Indicates that a geographic region derives its name from a specific person, place, event, or other entity.
-
E.
eraNameInJapanese
Indicates the Japanese-language name used for a specific historical or calendar era.
- 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_69a885fea6a481909fe83ba6441f1774 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a95b02cd448190be8e3db9a5a7bac0 |
completed | March 5, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_69a907c1cad08190b9728dd557f39aa0 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.