Triple
T24942354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Sea via Lake Lothing and Mutford Lock |
E623491
|
entity |
| Predicate | connectsSeaArea |
P49633
|
FINISHED |
| Object | North Sea off the Suffolk coast |
—
|
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: North Sea off the Suffolk coast | Statement: [North Sea via Lake Lothing and Mutford Lock, connectsSeaArea, North Sea off the Suffolk coast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsSeaArea Context triple: [North Sea via Lake Lothing and Mutford Lock, connectsSeaArea, North Sea off the Suffolk coast]
-
A.
connectsArea
Indicates that one area serves as a link or passage between two other areas, enabling movement or interaction between them.
-
B.
seaAreaCode
Indicates the specific coded maritime or sea area associated with or relevant to an entity.
-
C.
seaConnection
chosen
Indicates a relationship where two places are connected or accessible to each other via the sea, such as by maritime routes or coastal adjacency.
-
D.
hasAreaConnections
Indicates that an entity is linked to one or more surrounding or related areas, typically representing spatial or regional connections between them.
-
E.
appliesToSeaArea
Indicates that something (such as a rule, restriction, or designation) is relevant or valid within a specified sea area.
- 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_69e2fac6b5a48190a1c38857f00915a9 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f60c3b09488190ade1b69ff7f0df0e |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 18, 2026, 5:30 a.m.