Triple
T36068719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hōan |
E1043305
|
entity |
| Predicate | calendarEraType |
P36399
|
FINISHED |
| Object | regnal era name |
—
|
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: regnal era name | Statement: [Hōan, calendarEraType, regnal era name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: calendarEraType Context triple: [Hōan, calendarEraType, regnal era name]
-
A.
calendarEraAlignment
Indicates that two calendar eras are related by a defined temporal correspondence or offset, aligning their dates or time scales to each other.
-
B.
recurringEra
Indicates a relationship where a particular era or time period repeats or recurs, rather than occurring only once.
-
C.
calendarEpoch
Indicates the reference starting point in time from which a particular calendar system counts its dates.
-
D.
representsEra
chosen
Indicates that one entity designates the historical era, period, or age to which another entity belongs or is associated.
-
E.
prefersEra
Indicates a relationship where one entity favors or is more inclined toward a particular historical or cultural era over others.
- 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_69f76e2fd3248190b900d9a492bf5a7a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:08 p.m.