Triple
T9276843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GL postcode area |
E222968
|
entity |
| Predicate | containsPostTown |
P2711
|
FINISHED |
| Object | Lydney |
E72705
|
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: Lydney | Statement: [GL postcode area, containsPostTown, Lydney]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lydney Context triple: [GL postcode area, containsPostTown, Lydney]
-
A.
Lydney
chosen
Lydney is a small town in southwest England situated on the River Severn near the Forest of Dean.
-
B.
Lynndyl
Lynndyl is a small rural town located in central Utah in the western United States.
-
C.
Langden
Langden is an alternative spelling variant of the name Langdon, typically used as a surname or place name.
-
D.
Lydney Park
Lydney Park is a historic estate in Gloucestershire, England, known for its Roman temple complex, archaeological remains, and landscaped gardens.
-
E.
Hellingly
Hellingly is a village and civil parish in East Sussex, 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_69ca841ffe208190aa7bcffbef2f8379 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd07c95a98819098528b7ada37ddc1 |
completed | April 1, 2026, 11:55 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d09c467a2881909a4c4aafdc2490f0 |
completed | April 4, 2026, 5:06 a.m. |
Created at: March 30, 2026, 7:34 p.m.