Triple
T13030601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashford District |
E326428
|
entity |
| Predicate | hasSettlement |
P1068
|
FINISHED |
| Object | Charing |
E581855
|
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: Charing | Statement: [Ashford District, hasSettlement, Charing]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Charing Context triple: [Ashford District, hasSettlement, Charing]
-
A.
Charing
chosen
Charing is a historic village and civil parish in the Ashford district of Kent, England, situated on the Pilgrims' Way between Maidstone and Ashford.
-
B.
Charlton
Charlton is a district in southeast London known for its historic village center, riverside industrial heritage, and the football club Charlton Athletic.
-
C.
Charlton
Charlton is a small settlement located within the borough of Spelthorne in Surrey, England.
-
D.
Charlton
Charlton is a small town in upstate New York known for its rural character and residential communities.
-
E.
Churwell
Churwell is a village and suburb in West Yorkshire, England, situated near the town of Morley within the City of Leeds metropolitan area.
- 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_69d8076cc45c81908123123f43e69266 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97efd18308190877b3269403b36e2 |
completed | April 10, 2026, 10:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6c123c36c8190b3fbf9cbb3b7ecf9 |
completed | May 3, 2026, 3:29 a.m. |
Created at: April 9, 2026, 8:54 p.m.