Triple
T436237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Massachusetts Turnpike |
E10015
|
entity |
| Predicate | formerTollSystem |
P395
|
FINISHED |
| Object | ticket-based tolling |
—
|
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: ticket-based tolling | Statement: [Massachusetts Turnpike, formerTollSystem, ticket-based tolling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerTollSystem Context triple: [Massachusetts Turnpike, formerTollSystem, ticket-based tolling]
-
A.
tollingType
Indicates the specific method or basis by which a toll, fee, or charge is applied or calculated in a given context.
-
B.
fareSystem
chosen
Indicates a relationship where a system is used to determine, collect, or manage fares or payments for transportation or similar services.
-
C.
hasToll
Indicates that the use, access, or passage associated with something requires payment of a toll or fee.
-
D.
formerCallSign
Indicates that one identifier was previously used as the call sign for the other entity before being changed or replaced.
-
E.
fareType
Indicates the category or class of fare (such as standard, discounted, or promotional) that applies to a given trip, ticket, or pricing instance.
- 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_69a2e8465ef481909655c681b01e2986 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2ef0c97188190b62104cb639d4b60 |
completed | Feb. 28, 2026, 1:35 p.m. |
| PD | Predicate disambiguation | batch_69a2eddb98e081909efcf9f0a955a908 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.