Triple
T14113064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warburton |
E339692
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Lymm |
E34787
|
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: Lymm | Statement: [Warburton, locatedNear, Lymm]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lymm Context triple: [Warburton, locatedNear, Lymm]
-
A.
Lymm
chosen
Lymm is a picturesque village in Cheshire, England, known for its historic center, scenic waterways, and surrounding countryside.
-
B.
Bauple
Bauple is a small rural town in Queensland, Australia, known as the birthplace of the macadamia nut and situated within the Fraser Coast Region.
-
C.
Sandbach
Sandbach is a historic market town in Cheshire, England, noted for its Saxon crosses and traditional town centre.
-
D.
Wyre
Wyre is a small, sparsely populated island in the Orkney archipelago of Scotland, known for its tranquil landscape and archaeological sites.
-
E.
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.
- 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_69d81c6a95b481909e39111e0c1f31ee |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de600f992c81908133813f2894dcca |
completed | April 14, 2026, 3:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcd0b881388190a5bcdd87fd10c516 |
completed | May 7, 2026, 5:49 p.m. |
Created at: April 9, 2026, 10:22 p.m.