Triple
T6721612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allerdale |
E153407
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Flimby |
E557606
|
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: Flimby | Statement: [Allerdale, contains, Flimby]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Flimby Context triple: [Allerdale, contains, Flimby]
-
A.
Flimby
chosen
Flimby is a coastal village in Cumbria, England, situated between Maryport and Workington on the Irish Sea.
-
B.
Tealby
Tealby is a picturesque rural village in eastern England, known for its traditional stone cottages and scenic setting within the Lincolnshire countryside.
-
C.
Horbury
Horbury is a town in West Yorkshire, England, historically part of the Wakefield area and known for its industrial heritage and parish church.
-
D.
Waldringfield
Waldringfield is a small riverside village in eastern England known for its scenic setting on the River Deben and sailing activities.
-
E.
Thrupp
Thrupp is a small canal-side village in Oxfordshire, England, known for its historic wharf and picturesque setting along the Oxford Canal.
- 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_69c6880afb988190ad88011b48ecfcba |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d13861a08190ad19a16dcd76c908 |
completed | March 27, 2026, 6:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c700a14ebc819092cc40f522540f1a |
completed | March 27, 2026, 10:11 p.m. |
Created at: March 27, 2026, 2:07 p.m.