Triple
T25338027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russia and Japan |
E635328
|
entity |
| Predicate | haveTerritorialDisputeOver |
P62867
|
FINISHED |
| Object | Iturup Island |
—
|
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: Iturup Island | Statement: [Russia and Japan, haveTerritorialDisputeOver, Iturup Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveTerritorialDisputeOver Context triple: [Russia and Japan, haveTerritorialDisputeOver, Iturup Island]
-
A.
associatedTerritoryDispute
chosen
Indicates that there is a territorial dispute or contested claim connected to the referenced entity or relationship.
-
B.
borderDisputesWith
Indicates that there are contested or unresolved boundary claims between two entities.
-
C.
countryContestedBy
Indicates that control, ownership, or sovereignty over a country is disputed by multiple parties or entities.
-
D.
appliesToTerritorialDisputes
Indicates that a rule, agreement, or condition is relevant to or governs situations involving territorial disputes between parties.
-
E.
locatedInDisputedTerritory
Indicates that an entity is situated within a geographic area whose sovereignty or ownership is contested between two or more parties.
- 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_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:32 p.m.