Triple
T20258700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Willington |
E498772
|
entity |
| Predicate | nearbySettlement |
P350
|
FINISHED |
| Object | Repton |
—
|
NE NERFINISHED |
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: [Willington, nearbySettlement, Repton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Repton Context triple: [Willington, nearbySettlement, Repton]
-
A.
Repton
chosen
Repton is a historic English village in Derbyshire best known for its ancient abbey and prestigious Repton School.
-
B.
Repton
Repton is a small coastal village in New South Wales, Australia, situated near the Bellinger River and known for its beaches and relaxed rural atmosphere.
-
C.
Minworth
Minworth is a suburban village in the north-east of Birmingham, England, known for its industrial estates, residential areas, and proximity to major transport routes.
-
D.
Rustington
Rustington is a large coastal village and civil parish on the English Channel in the Arun District of West Sussex, England.
-
E.
Highworth
Highworth is a historic market town in Wiltshire, England, known for its elevated position and traditional architecture.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69da6275fa6c8190952924930adee150 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e674c84e848190a6e8956698b84026 |
completed | April 20, 2026, 6:47 p.m. |
Created at: April 11, 2026, 11:41 p.m.