Triple
T2329162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shōhō |
E48360
|
entity |
| Predicate | reclassificationDate |
P22032
|
FINISHED |
| Object | 22 January 1942 |
—
|
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: 22 January 1942 | Statement: [Shōhō, reclassificationDate, 22 January 1942]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reclassificationDate Context triple: [Shōhō, reclassificationDate, 22 January 1942]
-
A.
reclassificationYear
chosen
Indicates the year in which something was reassigned to a different category, status, or classification.
-
B.
redenominationDate
Indicates the date on which a currency or financial instrument undergoes a formal change in its nominal value or unit (redenomination).
-
C.
reclassifiedAs
Indicates that an entity’s classification or category has been changed from a previous one to a new one.
-
D.
reclassifiedBy
Indicates that an entity’s classification or category has been changed by a specific agent or authority.
-
E.
retrocessionDate
Indicates the date on which rights, obligations, or control previously transferred are formally returned or reassigned back to the original party or another designated party.
- 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_69a88aa308a88190b0b86c011fda7fce |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abcc30c5e881908c5d526d7e7491d0 |
completed | March 7, 2026, 6:56 a.m. |
| PD | Predicate disambiguation | batch_69abc5926d048190a535e3f23d41de2a |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:50 p.m.