Triple
T6522373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shildon |
E151214
|
entity |
| Predicate | hasPostTown |
P2711
|
FINISHED |
| Object | Shildon |
E151214
|
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: Shildon | Statement: [Shildon, hasPostTown, Shildon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shildon Context triple: [Shildon, hasPostTown, Shildon]
-
A.
Shildon
chosen
Shildon is a town in County Durham, England, historically significant as a cradle of the railway industry and home to major railway heritage attractions.
-
B.
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.
-
C.
Morpeth
Morpeth is a historic market town in Northumberland, England, known for its traditional architecture and role as a local commercial and administrative centre.
-
D.
Shenley
Shenley is a village and civil parish in the county of Hertfordshire in southern England, known for its residential character and proximity to London.
-
E.
Wallsend
Wallsend is a town in North Tyneside, England, historically significant as the eastern terminus of Hadrian’s Wall and site of the Segedunum Roman Fort.
- 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_69c687f522748190b3058405553cdabd |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ad95c2c88190b800aaaa73f99210 |
completed | March 27, 2026, 4:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6d5204e78819082bf991c2ece09df |
completed | March 27, 2026, 7:06 p.m. |
Created at: March 27, 2026, 1:45 p.m.