Triple
T10899299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tanzania and Burundi |
E257394
|
entity |
| Predicate | areLandlockedTogether |
P96301
|
FINISHED |
| Object | no |
—
|
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 | Statement: [Tanzania and Burundi, areLandlockedTogether, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areLandlockedTogether Context triple: [Tanzania and Burundi, areLandlockedTogether, no]
-
A.
isLandlockedByRoad
Indicates that a place has no direct road access to the broader road network except through another surrounding or enclosing region.
-
B.
sharesLandmassWith
Indicates that two geographic entities are located on the same continuous landmass or continent.
-
C.
landlocked
Indicates that a place has no direct access to the open sea or ocean, being entirely surrounded by land or enclosed bodies of water.
-
D.
geographicallyAdjacentTo
Indicates that two geographic entities share a common boundary or are directly next to each other in space.
-
E.
isLandlockedWithinIsland
Indicates that an entity has no direct access to the open sea and is entirely surrounded by land that itself is part of an island.
- F. None of above. chosen
Provenance (4 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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d761a2392c8190bc2c2359d63eff7a |
completed | April 9, 2026, 8:21 a.m. |
| PD | Predicate disambiguation | batch_69d70d3d69e08190bb369e9a7927142c |
completed | April 9, 2026, 2:21 a.m. |
| PDg | Predicate description generation | batch_69d7101de31c819090707635f6790559 |
completed | April 9, 2026, 2:34 a.m. |
Created at: April 8, 2026, 9:21 p.m.