Triple
T32424047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Korea–Japan relations |
E828527
|
entity |
| Predicate | JapanPolicyTool |
P174888
|
FINISHED |
| Object | economic sanctions |
—
|
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: economic sanctions | Statement: [North Korea–Japan relations, JapanPolicyTool, economic sanctions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: JapanPolicyTool Context triple: [North Korea–Japan relations, JapanPolicyTool, economic sanctions]
-
A.
accessPrefecture
Indicates that an entity has access to, or is associated with accessing, a specific prefecture.
-
B.
gdpRankInJapan
Indicates the position of an entity in the ordered ranking of GDP values within Japan.
-
C.
JapaneseAdvantage
Indicates that one party holds a comparative advantage or superior position specifically in a Japanese context (e.g., language, market, culture, or environment) relative to another.
-
D.
isPrefecturalCityOf
Indicates that a city holds the administrative status of a prefecture-level city within a given region or country.
-
E.
regionOfJapan
Indicates that one entity is a geographic region that is part of, or located within, Japan.
- 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_69f3491b28bc8190b75cea7a507f337b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c90790788190a1ed09adc86ed22d |
completed | May 3, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c814c26c81908f5c47285129ff2a |
completed | May 3, 2026, 3:59 a.m. |
Created at: May 1, 2026, 12:54 a.m.