Triple
T16661492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belmesthorpe |
E404869
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Ryhall |
E404869
|
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: Ryhall | Statement: [Belmesthorpe, locatedIn, Ryhall]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ryhall Context triple: [Belmesthorpe, locatedIn, Ryhall]
-
A.
Ryhall
chosen
Ryhall is a village and civil parish in the county of Rutland in the East Midlands of England.
-
B.
Ryhall
Ryhall is a village and civil parish in the South Kesteven district of Lincolnshire, England, known for its historic church and rural character.
-
C.
Tyvholm
Tyvholm is one of the small Danish islands that form part of the Hirsholmene archipelago in the Kattegat.
-
D.
Leyhof
Leyhof is a residential neighborhood in the Dutch town of Leiderdorp, located in the province of South Holland.
-
E.
Danderhall
Danderhall is a village in Midlothian, Scotland, situated just southeast of Edinburgh and functioning largely as a commuter community for the city.
- 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_69d8838b5fbc81908c6575c132b82e80 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37bfee5448190bb44c4dadba5dcbd |
completed | April 18, 2026, 12:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0084d091e0819088a98ef4aa775d07 |
completed | May 10, 2026, 1:14 p.m. |
Created at: April 10, 2026, 5:18 a.m.