Triple
T8147198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lymm Dam |
E190242
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Lymm Cross |
E183207
|
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 Cross | Statement: [Lymm Dam, near, Lymm Cross]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lymm Cross Context triple: [Lymm Dam, near, Lymm Cross]
-
A.
Lymm Cross
chosen
Lymm Cross is a historic stone cross and local landmark situated in the village centre of Lymm, Cheshire, England.
-
B.
Lenham Cross
Lenham Cross is a prominent hillside war memorial carved into the chalk downs above the village of Lenham in Kent, England.
-
C.
Crowborough Cross
Crowborough Cross is a central junction and notable local landmark in the town of Crowborough in East Sussex, England.
-
D.
Sandbach Crosses
The Sandbach Crosses are a pair of elaborately carved Anglo-Saxon stone crosses in Cheshire, England, renowned for their early medieval Christian artwork and historical significance.
-
E.
Banbury Cross
Banbury Cross is a historic market cross and well-known landmark in Banbury, Oxfordshire, famously associated with the English nursery rhyme "Ride a cock-horse to Banbury Cross."
- 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_69ca82be7ba8819087de0147e9292c83 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb447d6b1881908ff3fa25af6b4e80 |
completed | March 31, 2026, 3:50 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc94b667d88190a0b47c7e0e07f338 |
completed | April 1, 2026, 3:44 a.m. |
Created at: March 30, 2026, 5:36 p.m.