Triple
T5156036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Derbyshire |
E116310
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object | Repton |
E156363
|
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: Repton | Statement: [South Derbyshire, containsSettlement, Repton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Repton Context triple: [South Derbyshire, containsSettlement, Repton]
-
A.
Repton
chosen
Repton is a historic English village in Derbyshire best known for its ancient abbey and prestigious Repton School.
-
B.
Rustington
Rustington is a large coastal village and civil parish on the English Channel in the Arun District of West Sussex, England.
-
C.
Highworth
Highworth is a historic market town in Wiltshire, England, known for its elevated position and traditional architecture.
-
D.
Poynton
Poynton is a town in Cheshire, England, known for its former coal mining industry and distinctive shared-space central junction.
-
E.
Ropley
Ropley is a village in Hampshire, England, known for its heritage railway connections and rural countryside setting.
- 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_69bd445d94788190b72e2cc563120995 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79019c6481909641f173c5b3769a |
completed | March 20, 2026, 4:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bed0123bc48190920f60fc29f64734 |
completed | March 21, 2026, 5:06 p.m. |
Created at: March 20, 2026, 1:44 p.m.