Triple
T19833999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ryhope |
E476535
|
entity |
| Predicate | adjacentTo |
P224
|
FINISHED |
| Object | Seaham |
E204562
|
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: Seaham | Statement: [Ryhope, adjacentTo, Seaham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Seaham Context triple: [Ryhope, adjacentTo, Seaham]
-
A.
Seaham
Seaham is a small rural town in the Hunter Region of New South Wales, Australia, known for its historic buildings and riverside setting.
-
B.
Seaham
chosen
Seaham is a coastal town in North East England known for its seafront, historic harbor, and former coal mining heritage.
-
C.
Westgate-on-Sea
Westgate-on-Sea is a small seaside town on the north coast of Kent, England, known for its sandy beaches and Victorian architecture.
-
D.
Caister-on-Sea
Caister-on-Sea is a coastal village and popular holiday resort in Norfolk, England, known for its sandy beaches and historic lifeboat station.
-
E.
Hornsea
Hornsea is a small seaside town and former fishing village on the North Sea coast of the East Riding of Yorkshire in England, known for its beach, promenade, and nearby Hornsea Mere.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8e51c7c188190b926f3a2a7b5f881 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e656d0347c8190b586c7fe01b61e97 |
completed | April 20, 2026, 4:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a07ccd9b71c81909002a92d0e826510 |
completed | May 16, 2026, 1:48 a.m. |
Created at: April 10, 2026, 1:50 p.m.