Triple
T15666477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bellingham–Alaska route |
E377198
|
entity |
| Predicate | maritimeJurisdiction |
P4884
|
FINISHED |
| Object | U.S. territorial waters |
—
|
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: U.S. territorial waters | Statement: [Bellingham–Alaska route, maritimeJurisdiction, U.S. territorial waters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maritimeJurisdiction Context triple: [Bellingham–Alaska route, maritimeJurisdiction, U.S. territorial waters]
-
A.
maritimeDispute
Indicates a contested claim or disagreement between parties over maritime areas, boundaries, or rights.
-
B.
claimedAsTerritorialSeaBy
Indicates that a body of water is asserted by a state or authority to be part of its territorial sea.
-
C.
maritimeDomain
Indicates a relationship or activity that occurs within, affects, or is specifically associated with the maritime domain (seas, oceans, and related maritime operations).
-
D.
appliesToTerritorialWatersOf
chosen
Indicates that something (such as a rule, status, or condition) is applicable within the territorial waters of a specified entity.
-
E.
sharesMaritimeBorders
Indicates that two entities have adjacent territorial waters or maritime zones that touch or overlap, forming a shared sea boundary.
- 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_69d85cd2e28481909d4e975bee20872f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04f1151548190a14607e762686cb1 |
completed | April 16, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69deda8b36a4819081cb5708fe77ef51 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:16 a.m.