Triple
T16886750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teesside |
E421558
|
entity |
| Predicate | hasPort |
P35
|
FINISHED |
| Object | Teesport |
E728951
|
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: Teesport | Statement: [Teesside, hasPort, Teesport]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Teesport Context triple: [Teesside, hasPort, Teesport]
-
A.
Teesport
chosen
Teesport is a major deep-water port and industrial complex on the River Tees in North East England, serving as a key hub for bulk cargo, container traffic, and petrochemical industries.
-
B.
Southfleet
Southfleet is a small rural village and civil parish in north-west Kent, England, known for its historic church and traditional countryside setting.
-
C.
Tynemouth
Tynemouth is a coastal town in Tyne and Wear, England, known for its historic priory and castle overlooking long sandy beaches at the mouth of the River Tyne.
-
D.
Teesmouth
Teesmouth is the coastal estuary area where the River Tees meets the North Sea in northeast England, known for its industrial landscape and important wildlife habitats.
-
E.
Wearside
Wearside is an area in North East England centered on the city of Sunderland and the valley of the River Wear.
- 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_69d889d470fc8190b4aec199636c0c56 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3bbc1f42481909dcf595358c23497 |
completed | April 18, 2026, 5:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00cfca11bc8190b0835de0d56ca0b1 |
completed | May 10, 2026, 6:34 p.m. |
Created at: April 10, 2026, 5:29 a.m.