Triple
T29173924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snodland railway station |
E739548
|
entity |
| Predicate | isOnRiverValleyRoute |
P27424
|
FINISHED |
| Object | River Medway valley |
E38818
|
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: River Medway valley | Statement: [Snodland railway station, isOnRiverValleyRoute, River Medway valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnRiverValleyRoute Context triple: [Snodland railway station, isOnRiverValleyRoute, River Medway valley]
-
A.
isOnRiverIsland
Indicates that one entity (typically a place or structure) is located on an island situated within a river.
-
B.
isOnBorderRiver
Indicates that something is located along or directly adjacent to a river that forms a border between areas.
-
C.
hasSettlementOnRiver
Indicates that a settlement is located on or directly adjacent to a specific river.
-
D.
isOnIslandRoute
Indicates that something (such as a path, trip, or connection) follows a route that involves traveling to, from, or around an island.
-
E.
locatedInRiverValley
chosen
Indicates that something is situated within the geographical area of a river valley.
- F. None of above.
Provenance (4 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_69f07cb6394c8190ab7842c48e699e2a |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6633f165481909e68b69dea0a98a8 |
completed | May 2, 2026, 8:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a25890f78ac8190af6d4c153dfde22a |
completed | June 7, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:53 a.m.