Triple
T16532753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cheriton Terminal |
E401608
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Cheriton |
E397090
|
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: Cheriton | Statement: [Cheriton Terminal, locatedIn, Cheriton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cheriton Context triple: [Cheriton Terminal, locatedIn, Cheriton]
-
A.
Cheriton
chosen
Cheriton is a suburban area of Folkestone in Kent, England, known for its residential character and proximity to the Channel Tunnel terminal.
-
B.
Chapelton
Chapelton is a small town in central Jamaica known historically as an administrative and commercial center in the island’s interior.
-
C.
Chapelton
Chapelton is a small rural settlement in Devon, England, known for its location on the Tarka Line railway route.
-
D.
Richville
Richville is a small unincorporated community located in Morgan County in the U.S. state of Missouri.
-
E.
Carlysle
Carlysle is an alternative spelling of the surname and given name "Carlyle," which is of English and Scottish origin.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32ed97b0881909de106418aca8180 |
completed | April 18, 2026, 7:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a006093244081909ae74674de966d6d |
completed | May 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 5:15 a.m.