Triple
T14245470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Somali Exclusive Economic Zone |
E353120
|
entity |
| Predicate | innerBoundaryType |
P1972
|
FINISHED |
| Object | territorial sea limit |
—
|
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: territorial sea limit | Statement: [Somali Exclusive Economic Zone, innerBoundaryType, territorial sea limit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: innerBoundaryType Context triple: [Somali Exclusive Economic Zone, innerBoundaryType, territorial sea limit]
-
A.
innerBoundaryRegion
Indicates that one region serves as the inner boundary or enclosed area within another region or geometric entity.
-
B.
hasBoundaryType
chosen
Indicates that one entity has a boundary characterized by a specific type or classification in relation to another entity or context.
-
C.
boundaryCurrentType
Indicates the specific kind or classification of the current that exists at or across a boundary between regions or components.
-
D.
typicalBoundary
Indicates that one entity serves as the usual or characteristic boundary or limit for another entity.
-
E.
isBoundaryFor
Indicates that one entity serves as the limiting edge, border, or enclosing extent that defines the spatial or conceptual bounds of another entity.
- 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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de629464f88190817b190731bab156 |
completed | April 14, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69de05c09b7881908acbca18bd7d997c |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:08 a.m.