Triple
T8734094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mildmay |
E207330
|
entity |
| Predicate | adjacentTo |
P224
|
FINISHED |
| Object | Dalston |
E207329
|
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: Dalston | Statement: [Mildmay, adjacentTo, Dalston]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dalston Context triple: [Mildmay, adjacentTo, Dalston]
-
A.
Dalston
Dalston is a village in Cumbria, England, situated near Carlisle and known for its rural character and rail connections on the Cumbrian Coast Line.
-
B.
Dalston
chosen
Dalston is a vibrant, rapidly gentrifying district in East London known for its nightlife, diverse community, and creative arts scene.
-
C.
Shoreditch
Shoreditch is a vibrant East London district known for its creative industries, street art, nightlife, and tech startups.
-
D.
Stepney
Stepney is a historic district in the East End of London, England, known for its working-class roots and diverse immigrant communities.
-
E.
Islington
Islington is a vibrant inner London borough in England known for its dense urban character, cultural venues, and strong football heritage.
- 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_69ca8358e4008190898471a59b96c301 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d2a26988190acfda17f232e610a |
completed | March 31, 2026, 11:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf42bd840081908074e9d322a15b68 |
completed | April 3, 2026, 4:31 a.m. |
Created at: March 30, 2026, 6:37 p.m.