Triple
T560347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meiji Constitution |
E13435
|
entity |
| Predicate | reformProcess |
P10613
|
FINISHED |
| Object | post–World War II constitutional reform in Japan |
—
|
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: post–World War II constitutional reform in Japan | Statement: [Meiji Constitution, reformProcess, post–World War II constitutional reform in Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reformProcess Context triple: [Meiji Constitution, reformProcess, post–World War II constitutional reform in Japan]
-
A.
reform
Indicates bringing about significant changes to an existing system, practice, or entity in order to improve or correct it.
-
B.
scriptAfterReform
Indicates that one script or writing system is used after a reform or modification has been applied to another script.
-
C.
notableReform
Indicates that an entity is recognized for having initiated, led, or been central to a significant reform or transformative change in a system, policy, or institution.
-
D.
reformDate
Indicates the date on which a reform, change, or restructuring officially took effect or was implemented.
-
E.
postReformDevelopment
chosen
Indicates the development or changes that occur after a reform has been implemented.
- 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_69a4933edcf08190b35ecfd6014caee6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a499e13694819087a236bffa6601a9 |
completed | March 1, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69a494befb8481908bb4e2e9f31e343b |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.