Triple
T5928587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bridge House |
E131876
|
entity |
| Predicate | location |
P40
|
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: [Bridge House, location, Ambleside]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ambleside Context triple: [Bridge House, location, 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.
Homersfield
Homersfield is a small village and civil parish on the River Waveney in eastern England, known for its historic bridge and rural Suffolk setting.
-
C.
Broadmeadow
Broadmeadow is a suburb and major railway junction in Newcastle, New South Wales, Australia.
-
D.
Holytown
Holytown is a small village in North Lanarkshire, Scotland, situated near Motherwell and known primarily as a residential commuter community.
-
E.
Battisford
Battisford is a small rural village and civil parish located in the English county of Suffolk.
- 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_69c0085b75e88190a632f9691f9da48b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c038571d108190b4f3d242c068452f |
completed | March 22, 2026, 6:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0e3affd748190a37e3cc60e58d6a6 |
completed | March 23, 2026, 6:54 a.m. |
Created at: March 22, 2026, 4 p.m.