Triple
T32774551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Estonia |
E838158
|
entity |
| Predicate | hasExclusiveEconomicZoneIn |
P2047
|
FINISHED |
| Object | Baltic Sea |
—
|
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: Baltic Sea | Statement: [Estonia, hasExclusiveEconomicZoneIn, Baltic Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExclusiveEconomicZoneIn Context triple: [Estonia, hasExclusiveEconomicZoneIn, Baltic Sea]
-
A.
countryExclusiveEconomicZone
chosen
Indicates that a specified maritime area lies within the exclusive economic zone legally designated to a particular country.
-
B.
claimedAsTerritorialSeaBy
Indicates that a body of water is asserted by a state or authority to be part of its territorial sea.
-
C.
hasImportantEconomicZoneIn
Indicates that an entity possesses or controls a significant economic zone or area within the specified location.
-
D.
maximumBreadthOfExclusiveEconomicZone
Indicates the greatest width or extent of a state's exclusive economic zone from its baseline.
-
E.
hasOverseasTerritory
Indicates that one entity possesses or controls a territory located outside its own primary geographic or sovereign domain.
- 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_69f3493a824c8190938489ba69041d08 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 1, 2026, 1:13 a.m.