Triple
T15445720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lydbrook |
E370016
|
entity |
| Predicate | parish |
P2739
|
FINISHED |
| Object | Lydbrook civil parish |
E370016
|
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: Lydbrook civil parish | Statement: [Lydbrook, parish, Lydbrook civil parish]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lydbrook civil parish Context triple: [Lydbrook, parish, Lydbrook civil parish]
-
A.
Lydbrook
chosen
Lydbrook is a village in Gloucestershire, England, situated in the Wye Valley on the edge of the Forest of Dean and historically known for its coal mining and industrial heritage.
-
B.
Sudbrook
Sudbrook is a village in Monmouthshire, Wales, known for its historic role in the construction of the Severn Tunnel and its associated pumping station.
-
C.
Woolbrook
Woolbrook is a small rural locality in the New England region of New South Wales, Australia.
-
D.
Spitalbrook
Spitalbrook is a small settlement within the borough of Broxbourne in Hertfordshire, England.
-
E.
Deysbrook
Deysbrook is a small watercourse in Merseyside, England, that serves as one of the headwater streams feeding the River Alt.
- 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_69d85a19180081909925012fbf4e62a3 |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ef666e08190a02a01a676306ab9 |
completed | April 16, 2026, 1:44 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff21adb6b88190b573068bda223892 |
completed | May 9, 2026, 11:59 a.m. |
Created at: April 10, 2026, 3:21 a.m.