Triple
T14318874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BLR |
E355027
|
entity |
| Predicate | representsCountryLandlockedStatus |
P101856
|
FINISHED |
| Object | landlocked |
—
|
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: landlocked | Statement: [BLR, representsCountryLandlockedStatus, landlocked]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsCountryLandlockedStatus Context triple: [BLR, representsCountryLandlockedStatus, landlocked]
-
A.
hasLandlockedStatus
chosen
Indicates whether an entity is geographically landlocked, lacking direct access to the open sea or ocean.
-
B.
isLandlockedByRoad
Indicates that a place has no direct road access to the broader road network except through another surrounding or enclosing region.
-
C.
isLandlockedExceptForRiverBoundary
Indicates that an entity has no coastline on seas or oceans, except for a boundary formed by a river that connects (directly or indirectly) to such waters.
-
D.
isInLandlockedCountry
Indicates that the entity is located within a country that has no direct access to the ocean or sea.
-
E.
isInLandlockedRegion
Indicates that an entity is located within a geographic region that has no direct access to the ocean or sea.
- 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de883a93548190ac671b001d15d0bd |
completed | April 14, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69de2a9515f4819081aabf251bca5878 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:13 a.m.