Triple
T4592939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rugeley |
E103537
|
entity |
| Predicate | hasPostTown |
P2711
|
FINISHED |
| Object | RUGELEY |
E103537
|
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: RUGELEY | Statement: [Rugeley, hasPostTown, RUGELEY]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RUGELEY Context triple: [Rugeley, hasPostTown, RUGELEY]
-
A.
Rugeley
chosen
Rugeley is a market town in Staffordshire, England, historically known for its coal mining industry and location on the River Trent.
-
B.
Rudge
Rudge is a character from Alan Bennett’s play and film "The History Boys," known as one of the students whose academic potential is initially underestimated.
-
C.
Ruxley
Ruxley is a locality in the London Borough of Bromley, England, known for its mix of suburban development and nearby nature reserves such as the Ruxley Gravel Pits.
-
D.
Ropley
Ropley is a village in Hampshire, England, known for its heritage railway connections and rural countryside setting.
-
E.
Rowsley
Rowsley is a village in Derbyshire, England, known for its scenic location near the Peak District and its historic railway and riverside 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_69bd43dccaf08190aa89e9991a289719 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd593cf8508190acfc6ddb5716e80a |
completed | March 20, 2026, 2:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bde0d553f08190a56020e1bf8f700d |
completed | March 21, 2026, 12:05 a.m. |
Created at: March 20, 2026, 1:11 p.m.