Triple
T11795084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ribble catchment |
E280484
|
entity |
| Predicate | containsTown |
P847
|
FINISHED |
| Object | Kirkham |
E824463
|
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: Kirkham | Statement: [Ribble catchment, containsTown, Kirkham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kirkham Context triple: [Ribble catchment, containsTown, Kirkham]
-
A.
Kirkham
chosen
Kirkham is a small town in Lancashire, England, known historically for its textile industry and market-town character.
-
B.
Laleham
Laleham is a riverside village in Surrey, England, situated on the River Thames and known for its historic church, green spaces, and residential character.
-
C.
Oswaldkirk
Oswaldkirk is a small rural village and civil parish in North Yorkshire, England, known for its historic church and scenic countryside setting.
-
D.
Mirfield
Mirfield is a small town in West Yorkshire, England, known for its position on major rail routes and its historic textile industry.
-
E.
Ketteringham
Ketteringham is a small village and civil parish in Norfolk, England, known for its rural character and historic parish church.
- 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5a082d08190a42541396a06ed98 |
completed | April 10, 2026, 7:24 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f0911c2a40819088079fc286e4dc67 |
completed | April 28, 2026, 10:51 a.m. |
Created at: April 8, 2026, 9:42 p.m.