Triple
T4890799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wearside |
E109554
|
entity |
| Predicate | contains |
P35
|
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: [Wearside, contains, Seaham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Seaham Context triple: [Wearside, contains, 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.
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.
-
D.
Alnmouth
Alnmouth is a coastal village in Northumberland, England, known for its scenic beach, historic harbor, and role as a small railway stop on the route between Newcastle and Edinburgh.
-
E.
Seahouses
Seahouses is a coastal village and popular tourist resort on the North Sea in northern England, known as a gateway to the Farne Islands and for its fishing heritage.
- 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_69bd440f71348190b99938e59fb7f9a1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e07ca10819083f80f12374544b1 |
completed | March 20, 2026, 3:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be681a3d7881908120dc642af3f58a |
completed | March 21, 2026, 9:42 a.m. |
Created at: March 20, 2026, 1:28 p.m.