Triple
T3897090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Folkestone |
E90396
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | 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: Hythe | Statement: [Folkestone, near, Hythe]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hythe Context triple: [Folkestone, near, 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.
Brightlingsea
Brightlingsea is a coastal town in Essex, England, historically known for its maritime trade, shipbuilding, and association with the medieval Cinque Ports confederation.
-
C.
Yalding
Yalding is a historic rural village in Kent, England, known for its traditional architecture and location near the confluence of several rivers.
-
D.
Humbermede
Humbermede is a residential neighbourhood in the northwestern part of Toronto, Ontario, known for its diverse community and proximity to the Humber River.
-
E.
Tenterden
Tenterden is a historic market town in Kent, England, known for its traditional high street, heritage railway, and surrounding Wealden countryside.
- 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_69aed95d315881908cbf1bf4a7215fbf |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeecd34e608190bf1ca1d0c04562b2 |
completed | March 9, 2026, 3:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b51c9e3db881909e865e52a842b1be |
completed | March 14, 2026, 8:30 a.m. |
Created at: March 9, 2026, 3:21 p.m.