Triple
T6980142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Langworthy |
E161820
|
entity |
| Predicate | adjacentTo |
P224
|
FINISHED |
| Object | Weaste |
E29631
|
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: Weaste | Statement: [Langworthy, adjacentTo, Weaste]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Weaste Context triple: [Langworthy, adjacentTo, Weaste]
-
A.
Weaste
chosen
Weaste is a residential and industrial district within the city of Salford in Greater Manchester, England.
-
B.
Wyre
Wyre is a district and local government area in Lancashire, England, named after the River Wyre and known for its mix of coastal towns and rural countryside.
-
C.
Elswick
Elswick is a district in Newcastle upon Tyne, England, historically known as a major industrial and shipbuilding center.
-
D.
Tesseney
Tesseney is a town in western Eritrea near the Sudanese border, serving as a local commercial and agricultural center in the Gash-Barka region.
-
E.
Rippingale
Rippingale is a rural village and civil parish in the South Kesteven district of Lincolnshire, England.
- 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_69c68855dc0481909b4c7e9e9ed273db |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6db6c1efc8190ab1575ae2ce726db |
completed | March 27, 2026, 7:33 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c761bb90f48190882a58c2da10b3e4 |
completed | March 28, 2026, 5:06 a.m. |
Created at: March 27, 2026, 2:31 p.m.