Triple
T4923471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senior TT |
E110519
|
entity |
| Predicate | passesThrough |
P225
|
FINISHED |
| Object | Sulby |
E479703
|
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: Sulby | Statement: [Senior TT, passesThrough, Sulby]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sulby Context triple: [Senior TT, passesThrough, Sulby]
-
A.
Sulby
chosen
Sulby is a small village on the Isle of Man known for lying along the famous Snaefell Mountain Course used in the Isle of Man TT motorcycle races.
-
B.
Tealby
Tealby is a picturesque rural village in eastern England, known for its traditional stone cottages and scenic setting within the Lincolnshire countryside.
-
C.
Maltby
Maltby is an English surname of likely locational origin, associated with various places named Maltby in England.
-
D.
Wyre
Wyre is a district and local government area in Lancashire, England, named after the River Wyre and known for its mix of coastal towns and rural countryside.
-
E.
Brundall
Brundall is a village in Norfolk, England, known for its riverside location in the Norfolk Broads and its boating and leisure activities.
- 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_69bd4413f9908190afcff44d7929cc4c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ffd46748190843fed99f02fd8d5 |
completed | March 20, 2026, 4:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be77a6e1648190921487e3d81441b3 |
completed | March 21, 2026, 10:49 a.m. |
Created at: March 20, 2026, 1:30 p.m.