Triple
T5333019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walton Bridge |
E123354
|
entity |
| Predicate | crossesWatercourseType |
P56317
|
FINISHED |
| Object | non-tidal river reach of the 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: non-tidal river reach of the Thames | Statement: [Walton Bridge, crossesWatercourseType, non-tidal river reach of the Thames]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossesWatercourseType Context triple: [Walton Bridge, crossesWatercourseType, non-tidal river reach of the Thames]
-
A.
waterwayTypeCrossed
chosen
Indicates the specific kind of waterway (e.g., river, canal, stream) that is being crossed in the described relationship or action.
-
B.
crossesWaterBody
Indicates that an entity moves from one side of a water body to the other by passing over, through, or across it.
-
C.
crossesWatershed
Indicates that one entity passes from one drainage basin or watershed area into another, traversing the boundary between them.
-
D.
crossedByRiver
Indicates that a river passes across or through a specified area, feature, or route.
-
E.
hasBridgeTypeCrossing
Indicates that a bridge is characterized by a specific type of crossing it provides or supports.
- 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_69bd46477f9081909d242a327d749466 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85ac8e10819088b6a9e02d927044 |
completed | March 20, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69bd84583dbc819088a03e3afb30178c |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2 p.m.