Triple
T24568053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berwick Bridge |
E607848
|
entity |
| Predicate | wasMainRiverCrossingUntil |
P156378
|
FINISHED |
| Object | Royal Tweed Bridge opening in 1928 |
—
|
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: Royal Tweed Bridge opening in 1928 | Statement: [Berwick Bridge, wasMainRiverCrossingUntil, Royal Tweed Bridge opening in 1928]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasMainRiverCrossingUntil Context triple: [Berwick Bridge, wasMainRiverCrossingUntil, Royal Tweed Bridge opening in 1928]
-
A.
crossedByRiver
Indicates that a river passes across or through a specified area, feature, or route.
-
B.
waterwayTypeCrossed
Indicates the specific kind of waterway (e.g., river, canal, stream) that is being crossed in the described relationship or action.
-
C.
isOldestSurvivingBridgeAcross
Indicates that a bridge is the most ancient still-existing bridge that spans a specified waterway, road, or gap.
-
D.
wasCrossroadsOf
Indicates that a place served as a central junction or meeting point where multiple routes, paths, or influences converged.
-
E.
riverCrossedByAllies
Indicates that the river was traversed or crossed by allied forces.
- F. None of above. chosen
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_69e2c4cc35a48190990b7571bc086df8 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a9225d9c8190ae92e5540f6c45c2 |
completed | April 30, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
| PDg | Predicate description generation | batch_69f2a846c5bc81909ba50cee483bea91 |
completed | April 30, 2026, 12:54 a.m. |
Created at: April 18, 2026, 2:28 a.m.