Triple
T7597559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pendle Borough Council |
E179894
|
entity |
| Predicate | governsSettlement |
P760
|
FINISHED |
| Object | Earby |
E674846
|
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: Earby | Statement: [Pendle Borough Council, governsSettlement, Earby]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Earby Context triple: [Pendle Borough Council, governsSettlement, Earby]
-
A.
Earby
chosen
Earby is a small town in Lancashire, England, known historically for its textile industry and rural setting near the Yorkshire Dales.
-
B.
Ubley
Ubley is a small rural village in Somerset, England, situated near the northern edge of the Mendip Hills.
-
C.
Tealby
Tealby is a picturesque rural village in eastern England, known for its traditional stone cottages and scenic setting within the Lincolnshire countryside.
-
D.
Aywick
Aywick is a small coastal settlement on the island of Yell in Shetland, Scotland.
-
E.
Eastry
Eastry is a historic village and civil parish in Kent, England, known for its rural character and proximity to the coastal town of Deal.
- 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_69c69f3487ec8190bf7acdf2dd91e6d6 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9d4d3408190b9650347c7850c47 |
completed | March 27, 2026, 9:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c86846192c81909154e6cf60b21157 |
completed | March 28, 2026, 11:46 p.m. |
Created at: March 27, 2026, 3:53 p.m.