Triple
T25338091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Territories (Japan) |
E635329
|
entity |
| Predicate | unresolvedIssue |
P13650
|
FINISHED |
| Object | Japan–Russia peace treaty |
—
|
NE NERFINISHED |
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: Japan–Russia peace treaty | Statement: [Northern Territories (Japan), unresolvedIssue, Japan–Russia peace treaty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unresolvedIssue Context triple: [Northern Territories (Japan), unresolvedIssue, Japan–Russia peace treaty]
-
A.
notResolvedBy
Indicates that an issue, problem, or request remains unresolved despite the involvement or actions of a specified entity.
-
B.
involvesIssue
Indicates that an action, event, or entity is related to, concerns, or includes a particular issue.
-
C.
facingIssue
chosen
Indicates that an entity is currently experiencing, encountering, or dealing with a problem, difficulty, or obstacle.
-
D.
issueType
Indicates the specific category or classification assigned to an issue within a tracking or management context.
-
E.
concludingIssue
Indicates that an issue represents the final or closing installment in a sequence, series, or publication run.
- 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_69e75a99bd6481909476115b35b9a8e4 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f498b4cbb88190a8ac563ad1a73b5d |
completed | May 1, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
Created at: April 21, 2026, 1:32 p.m.