Triple
T30331543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashford–Ramsgate line |
E771492
|
entity |
| Predicate | connectsInlandTownsWith |
P108869
|
FINISHED |
| Object | Ramsgate |
—
|
NE NERFINISHED |
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: Ramsgate | Statement: [Ashford–Ramsgate line, connectsInlandTownsWith, Ramsgate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsInlandTownsWith Context triple: [Ashford–Ramsgate line, connectsInlandTownsWith, Ramsgate]
-
A.
connectsInlandRoutesTo
Indicates that one entity serves as a link or junction that enables inland transportation routes to reach or connect with another entity.
-
B.
connectsInlandCommunitiesTo
chosen
Indicates a relationship in which something serves as a link or conduit between inland communities and another place, system, or network.
-
C.
connectsInlandToBorder
Indicates that an inland location is linked or provides a route to a border location.
-
D.
connectsInlandCityToCoast
Indicates a relationship where a route, link, or infrastructure connects an inland city to a coastal area or city.
-
E.
connectsCoastToInland
Indicates a relationship where something (such as a route, structure, or feature) links a coastal area to an inland area.
- F. None of above.
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_69f2248aba24819095bb86480d55b23b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe031bc6208190860099aef72d8dcb |
completed | May 8, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69fe014c8b388190b5d4e0cb95ee2be5 |
completed | May 8, 2026, 3:29 p.m. |
Created at: April 29, 2026, 7:53 p.m.