Triple
T3102912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deal, Kent |
E64760
|
entity |
| Predicate | nearbySettlement |
P350
|
FINISHED |
| Object | Walmer, Kent |
E281209
|
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: Walmer, Kent | Statement: [Deal, Kent, nearbySettlement, Walmer, Kent]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Walmer, Kent Context triple: [Deal, Kent, nearbySettlement, Walmer, Kent]
-
A.
Walmer, Kent, England
chosen
Walmer in Kent, England, is a coastal town on the English Channel known for its historic castle and role as a seaside retreat.
-
B.
Halstead, Kent
Halstead, Kent is a small rural village and civil parish in the Sevenoaks District of Kent, England, known for its countryside setting on the North Downs.
-
C.
Gillingham, Kent
Gillingham, Kent is a town in southeast England on the River Medway, historically known for its naval dockyard and military connections.
-
D.
Chatham, Kent
Chatham, Kent is a historic town in southeast England, best known for its former Royal Navy dockyard and maritime heritage.
-
E.
Walmer
Walmer is a coastal town in Kent, England, known for its historic Walmer Castle and seafront overlooking the English Channel.
- 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_69ad857dc98481909e585dc3372e3ed5 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada26df128819086541db7680c8c24 |
completed | March 8, 2026, 4:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b20f5994088190abc4b56040922c16 |
completed | March 12, 2026, 12:56 a.m. |
Created at: March 8, 2026, 3:03 p.m.