Triple
T25162797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Man’en |
E626485
|
entity |
| Predicate | preModernJapaneseEraSequence |
P157975
|
FINISHED |
| Object | between Ansei and Bunkyū |
—
|
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: between Ansei and Bunkyū | Statement: [Man’en, preModernJapaneseEraSequence, between Ansei and Bunkyū]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preModernJapaneseEraSequence Context triple: [Man’en, preModernJapaneseEraSequence, between Ansei and Bunkyū]
-
A.
startOfNaraPeriod
Indicates that one event or time point marks the beginning of the Nara period in Japanese history.
-
B.
eraStartHeiseiYear
Indicates the calendar year in which the Heisei era begins for a given context or system of dating.
-
C.
preMeijiStatus
Indicates the status or condition an entity held prior to the Meiji period, typically in contrast to its later or modern status.
-
D.
timeOfAsukaPeriod
Indicates that the subject has a temporal association with, or occurs during, the Asuka historical period.
-
E.
startEraInJapaneseCalendar
Indicates the point in time when a specific era begins within the Japanese calendar system.
- 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_69e2ff2834ec8190b0872e2ec3d76023 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f46d401b988190848ff1e6bbc9f53a |
completed | May 1, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
| PDg | Predicate description generation | batch_69f45300bd488190bb1d4160f5534ef6 |
completed | May 1, 2026, 7:15 a.m. |
Created at: April 18, 2026, 6:31 a.m.