Triple
T5312207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Near Sawrey |
E119056
|
entity |
| Predicate | postalTown |
P2711
|
FINISHED |
| Object | AMBLESIDE |
E23647
|
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: AMBLESIDE | Statement: [Near Sawrey, postalTown, AMBLESIDE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: AMBLESIDE Context triple: [Near Sawrey, postalTown, AMBLESIDE]
-
A.
Ambleside
chosen
Ambleside is a popular town in England’s Lake District, known as a base for walking, boating on nearby Lake Windermere, and exploring the surrounding fells.
-
B.
Audlem
Audlem is a picturesque village and civil parish in Cheshire, England, known for its historic buildings, canal locks, and rural charm.
-
C.
Alcombe
Alcombe is a residential suburb and former village now forming part of the coastal town of Minehead in Somerset, England.
-
D.
Asthall
Asthall is a small historic village in Oxfordshire, England, known for its Cotswold stone architecture and association with the Mitford family.
-
E.
Ashbourne
Ashbourne is a historic market town in Derbyshire, England, known for its traditional architecture and annual Royal Shrovetide Football match.
- 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_69bd446b57bc8190a513d2e6c40314f3 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd8535a1ec819094b2c5d3cfc57f56 |
completed | March 20, 2026, 5:34 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf1106ef9c8190811f7b70e784c962 |
completed | March 21, 2026, 9:43 p.m. |
Created at: March 20, 2026, 1:54 p.m.