Triple
T8960897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Folkestone |
E213999
|
entity |
| Predicate | locatedNear |
P294
|
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, locatedNear, Hythe]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hythe Context triple: [Folkestone, locatedNear, 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.
Brightlingsea
Brightlingsea is a coastal town in Essex, England, historically known for its maritime trade, shipbuilding, and association with the medieval Cinque Ports confederation.
-
D.
Yalding
Yalding is a historic rural village in Kent, England, known for its traditional architecture and location near the confluence of several rivers.
-
E.
Bablock Hythe
Bablock Hythe is a historic riverside hamlet and former ferry crossing point on the River Thames in Oxfordshire, England.
- 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_69ca839cd6008190a1546a701a56710c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6748baa88190ac54e701dc4d6212 |
completed | April 1, 2026, 12:31 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfeb3680f88190a977ac4c103423f2 |
completed | April 3, 2026, 4:30 p.m. |
Created at: March 30, 2026, 7 p.m.