Triple

T37531308
Position Surface form Disambiguated ID Type / Status
Subject Nabunturan E933052 entity
Predicate hasLandlockedStatusReason P101856 FINISHED
Object no direct access to sea or coastline 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: no direct access to sea or coastline | Statement: [Nabunturan, hasLandlockedStatusReason, no direct access to sea or coastline]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLandlockedStatusReason
Context triple: [Nabunturan, hasLandlockedStatusReason, no direct access to sea or coastline]
  • A. hasLandlockedStatus chosen
    Indicates whether an entity is geographically landlocked, lacking direct access to the open sea or ocean.
  • B. isInLandlockedRegion
    Indicates that an entity is located within a geographic region that has no direct access to the ocean or sea.
  • C. isInLandlockedCountry
    Indicates that the entity is located within a country that has no direct access to the ocean or sea.
  • D. isLandlockedByRoad
    Indicates that a place has no direct road access to the broader road network except through another surrounding or enclosing region.
  • E. isInLandlockedProvince
    Indicates that the location or entity is situated within a province that has no direct access to the sea or ocean.
  • 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_69f76ec8862c8190bfa24145f5480642 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69ffe12ee59c8190bc7da386e6d5332d completed May 10, 2026, 1:36 a.m.
PD Predicate disambiguation batch_69ffe0a138bc8190a3d4b48cd579e985 completed May 10, 2026, 1:34 a.m.
Created at: May 3, 2026, 4:17 p.m.