Triple
T22740289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swinford Toll Bridge |
E562391
|
entity |
| Predicate | legalBasisForToll |
P149542
|
FINISHED |
| Object | historic Act of Parliament |
—
|
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: historic Act of Parliament | Statement: [Swinford Toll Bridge, legalBasisForToll, historic Act of Parliament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalBasisForToll Context triple: [Swinford Toll Bridge, legalBasisForToll, historic Act of Parliament]
-
A.
tollPurpose
Indicates that a toll is imposed for a specific purpose, such as funding, maintenance, or use of a particular facility or service.
-
B.
appliesTollTo
Indicates that a fee or charge is imposed on a subject for using, accessing, or passing through something.
-
C.
tollingType
Indicates the specific method or basis by which a toll, fee, or charge is applied or calculated in a given context.
-
D.
tollingAuthority
Indicates the entity that has the authority to impose, collect, or manage a toll on a given route, facility, or service.
-
E.
hasToll
Indicates that the use, access, or passage associated with something requires payment of a toll or fee.
- 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_69e245513a5c81908d5cb471b4fc429d |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1797241588190be67db7a37a88f23 |
completed | April 29, 2026, 3:22 a.m. |
| PD | Predicate disambiguation | batch_69eed2a971c0819088af574e40c9343f |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb5681f88190821129ced752f190 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:23 p.m.