Triple

T36378256
Position Surface form Disambiguated ID Type / Status
Subject River Blyth E895968 entity
Predicate emptiesInto P408 FINISHED
Object North Sea at Blyth
The North Sea at Blyth is the coastal area on England’s northeast shore where the River Blyth meets the open sea, known for its port, beaches, and offshore wind energy infrastructure.
E2180899 NE 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: North Sea at Blyth | Statement: [River Blyth, emptiesInto, North Sea at Blyth]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: North Sea at Blyth
Triple: [River Blyth, emptiesInto, North Sea at Blyth]
Generated description
The North Sea at Blyth is the coastal area on England’s northeast shore where the River Blyth meets the open sea, known for its port, beaches, and offshore wind energy infrastructure.

Provenance (5 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_69f76e51d358819092bbc5f119f49476 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7bb191af8819085752b8046efc840 completed May 3, 2026, 9:16 p.m.
NED1 Entity disambiguation (via context triple) batch_6a39a3400e948190acec96f7d08d943f completed June 22, 2026, 9:04 p.m.
NEDg Description generation batch_6a39a96ba5308190b8a3dfd67c304f54 completed June 22, 2026, 9:30 p.m.
NED2 Entity disambiguation (via description) batch_6a39a9c0e544819092a521ca7cd4cc64 completed June 22, 2026, 9:31 p.m.
Created at: May 3, 2026, 4:10 p.m.