Triple
T15605081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runcorn–Widnes Bridge |
E375137
|
entity |
| Predicate | tollStatusChange |
P119413
|
FINISHED |
| Object | tolls removed in 1961 |
—
|
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: tolls removed in 1961 | Statement: [Runcorn–Widnes Bridge, tollStatusChange, tolls removed in 1961]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tollStatusChange Context triple: [Runcorn–Widnes Bridge, tollStatusChange, tolls removed in 1961]
-
A.
tollSectionState
Indicates the status or condition of a specific toll road section within a tolling system.
-
B.
tollingType
Indicates the specific method or basis by which a toll, fee, or charge is applied or calculated in a given context.
-
C.
tollIntroduced
Indicates that a toll was established or put into effect for using a particular route, facility, or service.
-
D.
tollingBegan
Indicates that the period during which a time limit or deadline is suspended or paused has started.
-
E.
tollDevice
Indicates a device is used to collect or process tolls for passage on a road, bridge, or similar infrastructure.
- 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_69d85cce25008190b13b52745fbd719b |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e7d9328819090e93d55881269a5 |
completed | April 16, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f05f708190850f1d8782e132b0 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:12 a.m.