Triple
T16206867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enryaku |
E393349
|
entity |
| Predicate | eraNameType |
P122160
|
FINISHED |
| Object | year-naming system based on auspicious characters |
—
|
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: year-naming system based on auspicious characters | Statement: [Enryaku, eraNameType, year-naming system based on auspicious characters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraNameType Context triple: [Enryaku, eraNameType, year-naming system based on auspicious characters]
-
A.
eraName
Indicates the named historical or chronological era associated with an entity or time period.
-
B.
eraType
Indicates the classification of a time period or era according to its type or category.
-
C.
onomasticType
Indicates the specific kind or category of a name (e.g., personal, place, or other name type) that characterizes the naming relationship.
-
D.
eraNameInJapanese
Indicates the Japanese-language name used for a specific historical or calendar era.
-
E.
nameType
Indicates the specific category or type of a name associated with an entity (e.g., legal name, nickname, alias, or preferred name).
- 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e227101a3c819095ef40e50bf66433 |
completed | April 17, 2026, 12:26 p.m. |
| PD | Predicate disambiguation | batch_69e219e11f6081909106b1240a17fd37 |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e55a2388190b29a045a8c608ba4 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:03 a.m.