Triple
T15189441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Switch Island |
E362965
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Netherton |
E363154
|
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: Netherton | Statement: [Switch Island, locatedNear, Netherton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Netherton Context triple: [Switch Island, locatedNear, Netherton]
-
A.
Netherton
chosen
Netherton is a suburban area within the Metropolitan Borough of Sefton in Merseyside, England.
-
B.
Netherton
Netherton is a small rural village in Northumberland, England, situated in the scenic Coquet Valley.
-
C.
Netherton
Netherton is a village in West Yorkshire, England, situated within the metropolitan borough of the City of Wakefield.
-
D.
Netherton
Netherton is a suburban area and former industrial village in the West Midlands of England, historically known for coal mining and ironworks.
-
E.
Meckingsen
Meckingsen is a village-level district that forms part of the town of Soest in North Rhine-Westphalia, Germany.
- 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_69d85a09a39c81908759f23268e2d408 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0067beedc8190abc0a94c7a38f85e |
completed | April 15, 2026, 9:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fec89797ac819090fb68bb5f2fad5c |
completed | May 9, 2026, 5:39 a.m. |
Created at: April 10, 2026, 3:10 a.m.