Triple
T25338077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Territories (Japan) |
E635329
|
entity |
| Predicate | partOfLargerDispute |
P137668
|
FINISHED |
| Object | Kuril Islands dispute |
—
|
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: Kuril Islands dispute | Statement: [Northern Territories (Japan), partOfLargerDispute, Kuril Islands dispute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfLargerDispute Context triple: [Northern Territories (Japan), partOfLargerDispute, Kuril Islands dispute]
-
A.
partOfWiderDispute
chosen
Indicates that one dispute is a component or subset of a larger, overarching dispute or conflict.
-
B.
disputeInvolves
Indicates that a particular dispute includes or concerns the specified entities as participants or parties to the conflict.
-
C.
significantDispute
Indicates a serious, often prolonged disagreement or conflict exists between the involved entities.
-
D.
legalDisputeSubject
Indicates that a legal dispute concerns, involves, or is specifically about the referenced subject or matter.
-
E.
laterDisputedBy
Indicates that a previously made claim, statement, or assertion is subsequently challenged, questioned, or contradicted by another 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_69e75a99bd6481909476115b35b9a8e4 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 21, 2026, 1:32 p.m.