Triple
T25905729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Economy of Paraguay |
E652745
|
entity |
| Predicate | landlockedCountry |
P4368
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Economy of Paraguay, landlockedCountry, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landlockedCountry Context triple: [Economy of Paraguay, landlockedCountry, true]
-
A.
landlocked
chosen
Indicates that a place has no direct access to the open sea or ocean, being entirely surrounded by land or enclosed bodies of water.
-
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.
isLandlockedCity
Indicates that a city has no direct access to the sea or ocean, being entirely surrounded by land.
-
E.
areLandlockedTogether
Indicates that the entities share the condition of being landlocked, with 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_69e7ab3d3f8481909bc53ed64c06af33 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f603beb5248190aed52bf4e44f223c |
completed | May 2, 2026, 2:01 p.m. |
| PD | Predicate disambiguation | batch_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 22, 2026, 8:27 a.m.