Triple
T1234176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuril Islands |
E26507
|
entity |
| Predicate | hasUNLOCODERegion |
P3446
|
FINISHED |
| Object | RU-SAK |
—
|
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: RU-SAK | Statement: [Kuril Islands, hasUNLOCODERegion, RU-SAK]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUNLOCODERegion Context triple: [Kuril Islands, hasUNLOCODERegion, RU-SAK]
-
A.
hasUNLocode
Indicates that an entity is associated with a specific UN/LOCODE, identifying its location in the United Nations location code system.
-
B.
hasRegionCode
chosen
Indicates that an entity is associated with a specific regional identifier or code.
-
C.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
D.
isUNGeoschemeRegion
Indicates that a region is classified according to the United Nations geoscheme regional grouping system.
-
E.
hasPostalAddressRegion
Indicates the region component (such as state, province, or area) associated with an entity’s postal address.
- 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_69a4948571c88190a9191e451e6035fd |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be5d16ec819088056167c88d3318 |
completed | March 1, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69a4bb65d61c8190bf0424ea0019a98b |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.