Triple
T36896722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AutoExpreso |
E911908
|
entity |
| Predicate | tollCollectionType |
P73181
|
FINISHED |
| Object | open road 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: open road tolling | Statement: [AutoExpreso, tollCollectionType, open road tolling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tollCollectionType Context triple: [AutoExpreso, tollCollectionType, open road 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.
typeOfTollSystem
chosen
Indicates the specific kind or category of toll collection system used in a given context.
-
C.
tollCollectionSide
Indicates on which side (e.g., entry or exit, or direction of travel) a toll is collected in relation to a roadway or tolling point.
-
D.
tollRoadClass
Indicates the classification or category assigned to a toll road based on its type, characteristics, or tolling scheme.
-
E.
tollingAuthority
Indicates the entity that has the authority to impose, collect, or manage a toll on a given route, facility, or service.
- 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_69f76e841b54819097e7fa768bbc70b2 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd8e00c0819085b520069e25a5a3 |
completed | May 5, 2026, 2:24 p.m. |
| PD | Predicate disambiguation | batch_69f7cf79ddb08190a083405cccc14137 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.