Triple
T15234051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Itchen Bridge |
E364076
|
entity |
| Predicate | hasTollDiscountScheme |
P48119
|
FINISHED |
| Object | residents of Southampton |
—
|
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: residents of Southampton | Statement: [Itchen Bridge, hasTollDiscountScheme, residents of Southampton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTollDiscountScheme Context triple: [Itchen Bridge, hasTollDiscountScheme, residents of Southampton]
-
A.
hasTollVariant
Indicates that an entity has a version or instance that requires paying a toll or fee for use or access.
-
B.
hasToll
Indicates that the use, access, or passage associated with something requires payment of a toll or fee.
-
C.
hasTollSegment
Indicates that a route, road, or path includes a segment where a toll must be paid.
-
D.
tollExemption
chosen
Indicates that an entity is not required to pay a toll or fee that would normally be charged for using a particular route, facility, or service.
-
E.
appliesTollTo
Indicates that a fee or charge is imposed on a subject for using, accessing, or passing through something.
- 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_69d85a0ce24c81909c4d3b6475548c95 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007d7237081908dc17900ee66b64f |
completed | April 15, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69deca899d5c8190be4a7c71e1683c69 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:12 a.m.