Triple
T24568051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berwick Bridge |
E607848
|
entity |
| Predicate | isHistoricCrossingOf |
P138400
|
FINISHED |
| Object | River Tweed |
—
|
NE NERFINISHED |
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 Tweed | Statement: [Berwick Bridge, isHistoricCrossingOf, River Tweed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHistoricCrossingOf Context triple: [Berwick Bridge, isHistoricCrossingOf, River Tweed]
-
A.
isHistoricCrossing
chosen
Indicates that a crossing between two locations has historical significance, such as being notable in history, heritage, or past events.
-
B.
isHistoric
Indicates that something has significant importance or relevance in history, often due to its age, impact, or role in past events.
-
C.
crossingOf
Indicates that one entity serves as the intersection or crossing point of two or more linear features, such as roads, paths, or tracks.
-
D.
isHistoricSee
Indicates that one entity serves or functioned as a historically significant viewing point or place from which another entity is or was seen.
-
E.
historicalRegionCrossed
Indicates that one entity passes through or traverses the territory of a historically defined region.
- 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_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. |
Created at: April 18, 2026, 2:28 a.m.