Triple
T19129842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japan achieved income doubling ahead of schedule |
E468285
|
entity |
| Predicate | policyAnnouncementYear |
P134522
|
FINISHED |
| Object | 1960 |
—
|
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: 1960 | Statement: [Japan achieved income doubling ahead of schedule, policyAnnouncementYear, 1960]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policyAnnouncementYear Context triple: [Japan achieved income doubling ahead of schedule, policyAnnouncementYear, 1960]
-
A.
expansionAnnouncementYear
Indicates the year in which an expansion (such as a project, product, or service extension) was officially announced.
-
B.
authorizationYear
Indicates the year in which an official approval, permission, or authorization for something was granted.
-
C.
promotionYear
Indicates the year in which an entity was promoted to a new position, rank, or status.
-
D.
acquisitionAnnouncementYear
Indicates the calendar year in which an acquisition is publicly announced.
-
E.
marketingYear
Indicates the specific 12‑month period used for planning, recording, or analyzing marketing or sales activities for a product or market.
- 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e3e8c49481908b6be87af54d12cf |
completed | April 20, 2026, 8:29 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b085288190b974d649e12e0844 |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe8a06081909fd5c28a33e9f218 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:05 p.m.