Triple
T3644975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Bure |
E77275
|
entity |
| Predicate | hasSettlementOnBank |
P1010
|
FINISHED |
| Object | Horning |
E376252
|
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: Horning | Statement: [River Bure, hasSettlementOnBank, Horning]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Horning Context triple: [River Bure, hasSettlementOnBank, Horning]
-
A.
Horning
chosen
Horning is a picturesque village in Norfolk, England, known for its riverside setting within the Norfolk Broads.
-
B.
Wrey
Wrey is a variant spelling of the surname Wray, which is of English origin.
-
C.
Harrodstown
Harrodstown was the original pioneer settlement that later became Harrodsburg, recognized as one of the earliest permanent European-American communities in Kentucky.
-
D.
Haugesunder
A Haugesunder is a resident or native of the coastal city of Haugesund in western Norway.
-
E.
Orminge
Orminge is a residential district and commercial center in the eastern Stockholm urban area, located within Nacka Municipality in Sweden.
- 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_69ad85de1b988190a45f8dbfebc806fc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc35da84c81908950de92ba171fa3 |
completed | March 8, 2026, 6:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b48836f5d08190bbf0b6410ed6f766 |
completed | March 13, 2026, 9:57 p.m. |
Created at: March 8, 2026, 3:24 p.m.