Triple
T30278996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latvia–Estonia border |
E770033
|
entity |
| Predicate | maritimeBoundaryBody |
P119533
|
FINISHED |
| Object | Gulf of Riga |
—
|
NE NERFINISHED |
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: Gulf of Riga | Statement: [Latvia–Estonia border, maritimeBoundaryBody, Gulf of Riga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maritimeBoundaryBody Context triple: [Latvia–Estonia border, maritimeBoundaryBody, Gulf of Riga]
-
A.
maritimeBoundaryLengthApproxKm
Indicates the approximate length, measured in kilometers, of a state's maritime boundary or coastline.
-
B.
sharesMaritimeBorders
Indicates that two entities have adjacent territorial waters or maritime zones that touch or overlap, forming a shared sea boundary.
-
C.
maritimeBoundarySettledBy
Indicates that the maritime boundary between two entities has been formally determined and agreed upon through a specific decision, treaty, or authoritative process.
-
D.
claimedAsTerritorialSeaBy
Indicates that a body of water is asserted by a state or authority to be part of its territorial sea.
-
E.
containsMaritimeBoundaryLine
chosen
Indicates that one entity includes or encompasses a maritime boundary line that defines limits or divisions at 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_69f224868fa8819099127eaf8855a28f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 7:45 p.m.