Triple
T7611220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CT postcode area |
E172239
|
entity |
| Predicate | hasPostTown |
P2711
|
FINISHED |
| Object | West Hythe |
E83169
|
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: West Hythe | Statement: [CT postcode area, hasPostTown, West Hythe]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: West Hythe Context triple: [CT postcode area, hasPostTown, West Hythe]
-
A.
Hythe
chosen
Hythe is a historic coastal town in Kent, England, known as one of the original Cinque Ports that once played a key role in maritime defense and trade.
-
B.
Hythe
Hythe is a small village in northwestern Alberta, Canada, situated west of the city of Grande Prairie.
-
C.
Folkestone and Hythe
Folkestone and Hythe is a UK parliamentary constituency in Kent that covers the coastal towns of Folkestone and Hythe and their surrounding areas.
-
D.
Hythe, Hampshire
Hythe, Hampshire is a small coastal village and port on the western shore of Southampton Water in southern England, known for its historic pier and ferry link to Southampton.
-
E.
Hythe Quay
Hythe Quay is a historic waterfront area in Maldon, Essex, known for its traditional Thames sailing barges and maritime heritage.
- 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_69c6994f50808190ba228764bb422417 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6fa221c848190b892ba1caec8d83a |
completed | March 27, 2026, 9:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c868645f8081909439f63df3184628 |
completed | March 28, 2026, 11:46 p.m. |
Created at: March 27, 2026, 3:55 p.m.