Triple
T14798053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liscard |
E347829
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Egremont |
E364388
|
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: Egremont | Statement: [Liscard, near, Egremont]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Egremont Context triple: [Liscard, near, Egremont]
-
A.
Egremont
Egremont is a small rural town in southwestern Massachusetts known for its scenic Berkshire landscapes and historic New England character.
-
B.
Egremont
chosen
Egremont is a district within the town of Wallasey on the Wirral Peninsula in Merseyside, England.
-
C.
Uxbridge
Uxbridge is a suburban town in West London, England, known as a major commercial and administrative centre and the terminus of a branch of the London Underground.
-
D.
Uxbridge
Uxbridge is a township in Ontario, Canada, known for its rural landscapes, trail networks, and proximity to protected natural areas.
-
E.
Turnford
Turnford is a village and residential area in the Broxbourne district of Hertfordshire, England, forming part of the London commuter belt.
- 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_69d822ea8b7c819097dfadf3d45545e6 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decd6131f08190885f1d27b4bfac7a |
completed | April 14, 2026, 11:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe389183a881908e6af44b71f81ace |
completed | May 8, 2026, 7:25 p.m. |
Created at: April 10, 2026, 1:31 a.m.