Triple
T22238704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borough of Rugby |
E549660
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Wolston |
—
|
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: Wolston | Statement: [Borough of Rugby, contains, Wolston]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wolston Context triple: [Borough of Rugby, contains, Wolston]
-
A.
Wolston
chosen
Wolston is a village and civil parish in Warwickshire, England, situated between Coventry and Rugby.
-
B.
Woolston
Woolston is a riverside suburb of Christchurch, New Zealand, known historically for its industrial activity and proximity to the Heathcote River.
-
C.
Woolston
Woolston is a district of Southampton in Hampshire, England, historically known for its shipbuilding and marine engineering industries.
-
D.
Wilston
Wilston is an inner-northern residential suburb of Brisbane, Australia, known for its leafy streets, character homes, and proximity to the city centre.
-
E.
Yorton
Yorton is a small rural village in Shropshire, England, known for its modest railway station on the Crewe–Shrewsbury line.
- 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_69e11e4102b881909cf47d3768e25c19 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f132123a048190ba5a90d7acb9aeb2 |
completed | April 28, 2026, 10:17 p.m. |
Created at: April 16, 2026, 8:38 p.m.