Triple
T9140619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teesside urban area |
E219315
|
entity |
| Predicate | hasMajorTown |
P316
|
FINISHED |
| Object | Billingham |
E494568
|
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: Billingham | Statement: [Teesside urban area, hasMajorTown, Billingham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Billingham Context triple: [Teesside urban area, hasMajorTown, Billingham]
-
A.
Billingham
chosen
Billingham is an industrial town in County Durham, England, known historically for its chemical industry and proximity to the River Tees.
-
B.
Leamouth
Leamouth is a riverside district in East London where the River Lea meets the River Thames, known for its former industrial docks and recent waterside redevelopment.
-
C.
Buckhaven
Buckhaven is a coastal town in eastern Scotland, situated on the Firth of Forth in the historic county of Fife.
-
D.
Jaywick
Jaywick is a small coastal village in Essex, England, known for its seaside location and history of deprivation and flood risk.
-
E.
Blyth
Blyth is a coastal town and port in southeast Northumberland, England, known historically for coal mining and shipbuilding.
- 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_69ca83e012288190a5771058adbaabd2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8f2537881908956a9b0516e2d49 |
completed | April 1, 2026, 5:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d0480ee2f081908ed98844784e465c |
completed | April 3, 2026, 11:06 p.m. |
Created at: March 30, 2026, 7:19 p.m.