Triple
T1357604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Yare |
E29022
|
entity |
| Predicate | hasTownOnRiver |
P26693
|
FINISHED |
| Object | Brundall |
E160221
|
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: Brundall | Statement: [River Yare, hasTownOnRiver, Brundall]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Brundall Context triple: [River Yare, hasTownOnRiver, Brundall]
-
A.
Brundall
chosen
Brundall is a village in Norfolk, England, known for its riverside location in the Norfolk Broads and its boating and leisure activities.
-
B.
Buckland
Buckland is a small Inupiat community and city in northwestern Alaska situated along the Buckland River.
-
C.
Heanor
Heanor is a town in the Amber Valley district of Derbyshire, England, historically associated with coal mining and textile industries.
-
D.
Ribblehead
Ribblehead is a remote hamlet in North Yorkshire, England, best known for its dramatic moorland setting and the iconic Ribblehead Viaduct on the Settle–Carlisle railway.
-
E.
Mirfield
Mirfield is a small town in West Yorkshire, England, known for its position on major rail routes and its historic textile industry.
- 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_69a498d77abc8190913bf57e5f51d2c4 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c48e6534819090d23f3cc25093ae |
completed | March 1, 2026, 10:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ace566694c81909b07143855014884 |
completed | March 8, 2026, 2:56 a.m. |
Created at: March 1, 2026, 7:56 p.m.