Triple
T13709798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brent Eleigh |
E328738
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Bildeston |
E301434
|
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: Bildeston | Statement: [Brent Eleigh, locatedNear, Bildeston]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bildeston Context triple: [Brent Eleigh, locatedNear, Bildeston]
-
A.
Bildeston
chosen
Bildeston is a historic village and civil parish located in the county of Suffolk in eastern England.
-
B.
Denston
Denston is a small rural village and civil parish located in the county of Suffolk in eastern England.
-
C.
Brimpton
Brimpton is a rural village and civil parish in West Berkshire, England, known for its historic churches and countryside setting.
-
D.
Binsted
Binsted is a small rural village in West Sussex, England, known for its historic parish church of the Holy Cross and its surrounding countryside.
-
E.
Binsted
Binsted is a rural civil parish and village in East Hampshire, England, known for its countryside setting and historic 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_69d80770b9bc81909f70c8c317d53cff |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dd43949e6c8190ae5e4fa119cde33a |
completed | April 13, 2026, 7:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f79d52b3708190ae0945e65b271556 |
completed | May 3, 2026, 7:09 p.m. |
Created at: April 9, 2026, 9:54 p.m.