Triple
T30840716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | селище Біле |
E785499
|
entity |
| Predicate | partOfTerritorialWatersOf |
P199171
|
FINISHED |
| Object | Україна |
—
|
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: Україна | Statement: [селище Біле, partOfTerritorialWatersOf, Україна]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfTerritorialWatersOf Context triple: [селище Біле, partOfTerritorialWatersOf, Україна]
-
A.
claimedAsTerritorialSeaBy
Indicates that a body of water is asserted by a state or authority to be part of its territorial sea.
-
B.
separatesTerritorialWatersOf
Indicates that one entity (typically a body of water or boundary) serves as a dividing line between the territorial waters of two or more distinct entities.
-
C.
hasTerritorialSeaIn
Indicates that an entity’s territorial sea is located within or extends into the area or jurisdiction of another entity.
-
D.
appliesToTerritorialWatersOf
Indicates that something (such as a rule, status, or condition) is applicable within the territorial waters of a specified entity.
-
E.
borderingSeaAreaOf
Indicates that one entity is a sea area that directly borders or adjoins the coastline or maritime boundary of another entity.
- 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_69f224b73d8c81908129383bfb397c87 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff246e0d4481908bcec718e1d4025b |
completed | May 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69ff23cb70ac81909b776ace4597ae9c |
completed | May 9, 2026, 12:08 p.m. |
| PDg | Predicate description generation | batch_69ff246d53cc81909d5528224149b04b |
completed | May 9, 2026, 12:11 p.m. |
Created at: April 29, 2026, 8:45 p.m.