Triple
T16985875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deritend Bridge |
E412062
|
entity |
| Predicate | riverCrossedInCity |
P104419
|
FINISHED |
| Object | River Rea in Birmingham |
—
|
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: River Rea in Birmingham | Statement: [Deritend Bridge, riverCrossedInCity, River Rea in Birmingham]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverCrossedInCity Context triple: [Deritend Bridge, riverCrossedInCity, River Rea in Birmingham]
-
A.
crossedByRiver
Indicates that a river passes across or through a specified area, feature, or route.
-
B.
hasRiverCrossingNearby
Indicates that there is a river crossing located in close proximity to the referenced entity or location.
-
C.
waterwayTypeCrossed
Indicates the specific kind of waterway (e.g., river, canal, stream) that is being crossed in the described relationship or action.
-
D.
hasCanalCrossing
Indicates that one entity is connected to or traversed by another via a canal crossing, such as a bridge, aqueduct, or similar structure over a canal.
-
E.
hasRiverCrossingType
chosen
Indicates the type or nature of a river crossing associated with an entity (e.g., bridge, ford, ferry).
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d18af95c8190a25ef0614e1a17f3 |
completed | April 18, 2026, 6:46 p.m. |
| PD | Predicate disambiguation | batch_69e35d4dff4881909b384e30f2d36bff |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:32 a.m.