Triple
T13851530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Croydon South |
E332954
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Coulsdon |
—
|
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: Coulsdon | Statement: [Croydon South, contains, Coulsdon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Coulsdon Context triple: [Croydon South, contains, Coulsdon]
-
A.
Coulsdon
chosen
Coulsdon is a suburban town in the London Borough of Croydon, England, known for its residential character and proximity to the North Downs.
-
B.
Beddington
Beddington is a suburban area in South London known for its historic village core, green spaces, and proximity to Croydon and central London.
-
C.
Coulsdon Common
Coulsdon Common is a large public open space and nature reserve in the Coulsdon area of south London, known for its woodlands, grasslands, and walking trails.
-
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.
Sellindge
Sellindge is a rural village in Kent, England, situated between Ashford and Folkestone and known for its community amenities and surrounding countryside.
- 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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02da9460819093a3ec5a3c62ea81 |
completed | April 14, 2026, 9:03 a.m. |
Created at: April 9, 2026, 10:14 p.m.