Triple
T2688080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tyne and Wear |
E57532
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Tynemouth |
E176442
|
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: Tynemouth | Statement: [Tyne and Wear, contains, Tynemouth]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tynemouth Context triple: [Tyne and Wear, contains, Tynemouth]
-
A.
Tynemouth
chosen
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.
-
B.
Hartlepool
Hartlepool is a coastal town in County Durham, England, known historically for its shipbuilding and maritime heritage.
-
C.
Maryport
Maryport is a coastal town in Cumbria, England, known for its historic harbor, Roman heritage, and maritime history.
-
D.
South Shields
South Shields is a coastal town in Tyne and Wear, England, known historically for its shipbuilding and as part of the Tyneside urban area.
-
E.
Newcastle upon Tyne
Newcastle upon Tyne is a major city in northeast England known for its industrial heritage, iconic Tyne Bridge, and vibrant cultural and nightlife scenes.
- 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_69ab4a5028388190a36f3baf1588309e |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd9f1ba3081909a349a2f30f8f9c9 |
completed | March 7, 2026, 7:55 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afaf5b19b88190982a669501463fa9 |
completed | March 10, 2026, 5:42 a.m. |
Created at: March 6, 2026, 9:54 p.m.