Triple
T8734088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mildmay |
E207330
|
entity |
| Predicate | partOf |
P40
|
FINISHED |
| Object | Islington |
E391232
|
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: Islington | Statement: [Mildmay, partOf, Islington]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Islington Context triple: [Mildmay, partOf, Islington]
-
A.
Islington
chosen
Islington is a vibrant inner London borough in England known for its dense urban character, cultural venues, and strong football heritage.
-
B.
Islington
Islington is a village within the town of Westwood, Massachusetts, known as one of its primary residential neighborhoods.
-
C.
Finsbury
Finsbury is an inner-city district of central London, historically part of the London Borough of Islington and known for its dense urban character and proximity to the City of London.
-
D.
Redbridge
Redbridge is a borough in northeast London, England, known for its suburban character, green spaces, and diverse communities.
-
E.
Highbury & Islington
Highbury & Islington is a major London transport hub in Islington served by London Underground, London Overground, and National Rail services.
- 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_69d178a6467c8190aab201fb12d2a64e |
completed | April 4, 2026, 8:46 p.m. |
Created at: March 30, 2026, 6:37 p.m.