Triple
T38013009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ringwould, Kent, England |
E948415
|
entity |
| Predicate | nearbyCoastalTown |
P193650
|
FINISHED |
| Object | Walmer, Kent, England |
—
|
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: Walmer, Kent, England | Statement: [Ringwould, Kent, England, nearbyCoastalTown, Walmer, Kent, England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyCoastalTown Context triple: [Ringwould, Kent, England, nearbyCoastalTown, Walmer, Kent, England]
-
A.
nearestCoastalTown
Indicates that one town is the closest coastal town geographically relative to a given reference location or town.
-
B.
nearestCoastalCity
Indicates that one city is the closest coastal city to another location or city, based on geographic distance.
-
C.
hasNearbyCoast
Indicates that one location is situated close to a coastline or seashore.
-
D.
nearbyCityOrPort
Indicates that one location is geographically close to a city or port, typically within a short travel distance.
-
E.
hasNearbyCoastalSettlement
chosen
Indicates that one entity has a coastal settlement located in close geographic proximity to it.
- 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_69f76efb4b10819092c8c2ba28ac06a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff27b125948190aced0fe0189fd39a |
completed | May 9, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69ff26c30a0481909ef6a54ded851e42 |
completed | May 9, 2026, 12:21 p.m. |
Created at: May 3, 2026, 4:20 p.m.