Triple
T32424043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Korea–Japan relations |
E828527
|
entity |
| Predicate | PyongyangDeclarationDate |
P104514
|
FINISHED |
| Object | 2002-09-17 |
—
|
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: 2002-09-17 | Statement: [North Korea–Japan relations, PyongyangDeclarationDate, 2002-09-17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PyongyangDeclarationDate Context triple: [North Korea–Japan relations, PyongyangDeclarationDate, 2002-09-17]
-
A.
peaceDeclarationDate
Indicates the date on which a formal declaration of peace between the involved parties was made.
-
B.
treatyDate
Indicates the calendar date on which a treaty is formally agreed upon, signed, or comes into effect between parties.
-
C.
dateOfFirstProclamation
chosen
Indicates the specific date on which something (such as a law, declaration, or official statement) was first formally proclaimed or announced.
-
D.
peaceAccordDate
Indicates the date on which a formal peace accord between parties was signed or came into effect.
-
E.
PetersbergDeclarationYear
Indicates the year in which a given Petersberg Declaration was formally adopted or issued.
- 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_69f3491b28bc8190b75cea7a507f337b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c28583648190adf17b19c29515c8 |
completed | May 3, 2026, 3:35 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:54 a.m.