Triple
T13506031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Folkestone and Hythe |
E321016
|
entity |
| Predicate | covers |
P1393
|
FINISHED |
| Object | Sandgate |
E397091
|
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: Sandgate | Statement: [Folkestone and Hythe, covers, Sandgate]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sandgate Context triple: [Folkestone and Hythe, covers, Sandgate]
-
A.
Sandgate
Sandgate is a railway station serving the suburb of Sandgate in the Newcastle region of New South Wales, Australia.
-
B.
Sandgate
chosen
Sandgate is a coastal village and suburb in Kent, England, known for its shingle beach, historic seafront, and proximity to the town of Folkestone.
-
C.
Whitegate
Whitegate is a residential suburb within the town of Chadderton in Greater Manchester, England.
-
D.
Wallgate
Wallgate is a street in the center of Wigan, England, known for giving its name to the nearby Wigan Wallgate railway station.
-
E.
Șchei Gate
Șchei Gate is a historic city gate in Brașov, Romania, marking the entrance to the old Șchei district and serving as a notable example of the city's medieval fortifications.
- 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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf8259a08190ada13c4a3078f07d |
completed | April 12, 2026, 2:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f75d9009688190b8f18bb3525c6afd |
completed | May 3, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:43 p.m.