Triple
T31078817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lithuanian exclusive economic zone |
E792045
|
entity |
| Predicate | borderingSeaAreaOf |
P197848
|
FINISHED |
| Object | Latvian exclusive economic zone |
—
|
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: Latvian exclusive economic zone | Statement: [Lithuanian exclusive economic zone, borderingSeaAreaOf, Latvian exclusive economic zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderingSeaAreaOf Context triple: [Lithuanian exclusive economic zone, borderingSeaAreaOf, Latvian exclusive economic zone]
-
A.
hasLandBorderWithSea
Indicates that an entity’s land area directly borders or touches a sea along its coastline.
-
B.
hasTerritorialSeaIn
Indicates that an entity’s territorial sea is located within or extends into the area or jurisdiction of another entity.
-
C.
isPartOfCoastOf
Indicates that one entity forms a segment or component of the coastline belonging to another entity.
-
D.
seaSeparatedFrom
Indicates that one geographic region or landmass is separated from another by a sea lying between them.
-
E.
hasCoastlineOn
Indicates that one entity’s coastline borders or is directly adjacent to a specified body of water.
- 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69feb342994081909481ec8ec5d44928 |
completed | May 9, 2026, 4:08 a.m. |
| PD | Predicate disambiguation | batch_69feb046e4e48190b96649aa28529cc9 |
completed | May 9, 2026, 3:55 a.m. |
| PDg | Predicate description generation | batch_69feb3419158819082f4666077535ca9 |
completed | May 9, 2026, 4:08 a.m. |
Created at: April 29, 2026, 9:02 p.m.