Triple
T29424018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chertsey Lock |
E746235
|
entity |
| Predicate | weirLocatedOn |
P1489
|
FINISHED |
| Object | right bank of the River Thames |
—
|
LITERAL 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: right bank of the River Thames | Statement: [Chertsey Lock, weirLocatedOn, right bank of the River Thames]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weirLocatedOn Context triple: [Chertsey Lock, weirLocatedOn, right bank of the River Thames]
-
A.
locatedOnTributaryOf
Indicates that one entity is situated along or on the banks of a tributary that flows into another specified water body.
-
B.
isCentralWaterfrontOf
Indicates that one location serves as the primary waterfront area or main waterside district of another place.
-
C.
locatedOnWaterbody
chosen
Indicates that an entity is situated on or directly adjacent to a specified body of water.
-
D.
waterfallLocation
Indicates the spatial location or geographic area where a waterfall is situated.
-
E.
waterwayServed
Indicates that a place, facility, or infrastructure is served by, connected to, or functionally supported by a particular waterway.
- 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_69f0a7a06e0081908add494075912eb4 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66a6b7dc081909b1a42c61272cc6b |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 3:07 p.m.