Triple
T8780914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coulsdon |
E208722
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Purley |
E501091
|
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: Purley | Statement: [Coulsdon, near, Purley]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Purley Context triple: [Coulsdon, near, Purley]
-
A.
Purley
chosen
Purley is a suburban town in South London known for its residential character and location within the London Borough of Croydon.
-
B.
Hounslow
Hounslow is a suburban district in West London known for its diverse community, major transport links, and proximity to Heathrow Airport.
-
C.
Surbiton
Surbiton is a suburban area in southwest London, England, known for its commuter links to central London and its leafy residential character.
-
D.
Burgess Hill
Burgess Hill is a town in southeastern England known as a commuter hub with residential areas and light industry, situated within the county of West Sussex.
-
E.
Harmondsworth
Harmondsworth is a village in the London Borough of Hillingdon, England, known for its historic Great Barn and proximity to Heathrow Airport.
- 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_69ca835fbee88190bf625939bac48d7f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f55b7b08190ab3e18cd634a144b |
completed | March 31, 2026, 11:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d3549788608190a1949eb254e43a8e |
completed | April 6, 2026, 6:37 a.m. |
Created at: March 30, 2026, 6:42 p.m.