Triple
T21925740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wealden (UK Parliament constituency) |
E541439
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object | Heathfield |
—
|
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: Heathfield | Statement: [Wealden (UK Parliament constituency), containsSettlement, Heathfield]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Heathfield Context triple: [Wealden (UK Parliament constituency), containsSettlement, Heathfield]
-
A.
Heathfield
Heathfield is a district in Birmingham, England, historically notable as the place where pioneering engineer James Watt spent his final years and died.
-
B.
Heathfield
chosen
Heathfield is a small market town in East Sussex, England, known for its rural surroundings and community-focused local events.
-
C.
Heathfield
Heathfield is a residential suburb located within the Southern Suburbs region of Cape Town, South Africa.
-
D.
Heathfield
Heathfield is a residential suburb and ward in the London Borough of Croydon in south London, England.
-
E.
Heathfield
Heathfield is a small locality in the Adelaide Hills region of South Australia, known for its semi-rural setting and proximity to the city of Adelaide.
- 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_69e0c47d74488190a15119108794a307 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f123fa40c48190b80a85e562ea2591 |
completed | April 28, 2026, 9:17 p.m. |
Created at: April 16, 2026, 7:46 p.m.