Triple
T13731470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Langcliffe |
E329809
|
entity |
| Predicate | civilParish |
P2739
|
FINISHED |
| Object | Langcliffe |
E329809
|
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: Langcliffe | Statement: [Langcliffe, civilParish, Langcliffe]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Langcliffe Context triple: [Langcliffe, civilParish, Langcliffe]
-
A.
Langcliffe
chosen
Langcliffe is a small village in North Yorkshire, England, situated in the scenic Yorkshire Dales near the market town of Settle.
-
B.
Trottiscliffe
Trottiscliffe is a small rural village in Kent, England, known for its historic church and proximity to the Neolithic Coldrum Long Barrow.
-
C.
Roecliffe
Roecliffe is a small village in North Yorkshire, England, known for its rural setting near the River Ure and traditional English countryside character.
-
D.
Briercliffe
Briercliffe is a civil parish and rural village area in Lancashire, England, situated within the Borough of Burnley.
-
E.
Clanfield
Clanfield is a rural village in Hampshire, England, situated within the South Downs and known for its scenic countryside and residential community.
- 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_69d80772315881908f980cae40d91664 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69de01f92b588190be97ec4564dddd59 |
completed | April 14, 2026, 8:59 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7a84c02e08190b8ef620575157c14 |
completed | May 3, 2026, 7:55 p.m. |
Created at: April 9, 2026, 9:55 p.m.