Triple
T17162135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Territories |
E416505
|
entity |
| Predicate | regionClaimedAs |
P647
|
FINISHED |
| Object | Northern Japan |
—
|
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: Northern Japan | Statement: [Northern Territories, regionClaimedAs, Northern Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionClaimedAs Context triple: [Northern Territories, regionClaimedAs, Northern Japan]
-
A.
includesAreaClaimedAs
Indicates that one entity encompasses or contains an area that is claimed as belonging to another entity.
-
B.
claimedAs
Indicates that one entity asserts ownership, authorship, responsibility, or some other form of association over another entity.
-
C.
claimsTerritory
chosen
Indicates that one entity asserts ownership, control, or sovereign rights over a specific geographic area or region.
-
D.
claimedFor
Indicates that one entity has asserted ownership, responsibility, or entitlement over or on behalf of another entity.
-
E.
regionAtStake
Indicates that a specific geographic or political area is the subject of contention, risk, or negotiation within a given situation or interaction.
- 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_69d886d279c081909f8ff1f743ddeb69 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f91258648190a40396067ba5ecd3 |
completed | April 18, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69e3830d2a90819092386717dc56f0e8 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:37 a.m.