Triple
T26685342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pennsylvania Turnpike |
E672727
|
entity |
| Predicate | tollCollectionBrand |
P37451
|
FINISHED |
| Object | E-ZPass |
—
|
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: E-ZPass | Statement: [Pennsylvania Turnpike, tollCollectionBrand, E-ZPass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tollCollectionBrand Context triple: [Pennsylvania Turnpike, tollCollectionBrand, E-ZPass]
-
A.
electronicTollBrand
chosen
Indicates that an entity is associated with or accepts a particular brand of electronic toll collection system.
-
B.
tollingAuthority
Indicates the entity that has the authority to impose, collect, or manage a toll on a given route, facility, or service.
-
C.
hasTollAgency
Indicates that a transportation facility or route is operated, managed, or overseen by a specific toll-collecting agency.
-
D.
typeOfTollSystem
Indicates the specific kind or category of toll collection system used in a given context.
-
E.
tollRoadOf
Indicates that a road segment is a toll road belonging to or associated with a particular roadway, route, or transportation network.
- 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_69eecda2066c8190a344218afa5e89c1 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6173d46088190859dd8292d078771 |
completed | May 2, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:22 a.m.