Triple
T22440173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 上皇 |
E554732
|
entity |
| Predicate | dateOfModernRestoration |
P8589
|
FINISHED |
| Object | 2019年5月1日以降の制度運用で明確化 |
—
|
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: 2019年5月1日以降の制度運用で明確化 | Statement: [上皇, dateOfModernRestoration, 2019年5月1日以降の制度運用で明確化]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfModernRestoration Context triple: [上皇, dateOfModernRestoration, 2019年5月1日以降の制度運用で明確化]
-
A.
reconstructionOrRestorationDate
chosen
Indicates the date on which an entity was reconstructed or restored after damage, alteration, or deterioration.
-
B.
restorationProject
Indicates a project whose purpose is to repair, renew, or return something to a previous or improved condition.
-
C.
rebuiltOrModifiedDuring
Indicates that an existing entity was reconstructed, renovated, or otherwise significantly altered during a specified time period or event.
-
D.
currentStructureIsModernReconstruction
Indicates that the existing structure is a modern reconstruction rather than the original historical building.
-
E.
renovatedBy
Indicates that an entity has been improved, restored, or updated through renovation work performed by another entity.
- 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_69e11e5010e48190ae1e9c9db9697637 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ae0edcc8190919b198035de0df2 |
completed | April 29, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69e898a327948190beee5e168006a0a7 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:47 p.m.