Triple
T37900794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PIKEPASS |
E945405
|
entity |
| Predicate | hasTollTagFormFactor |
P195029
|
FINISHED |
| Object | windshield-mounted transponder |
—
|
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: windshield-mounted transponder | Statement: [PIKEPASS, hasTollTagFormFactor, windshield-mounted transponder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTollTagFormFactor Context triple: [PIKEPASS, hasTollTagFormFactor, windshield-mounted transponder]
-
A.
hasToll
Indicates that the use, access, or passage associated with something requires payment of a toll or fee.
-
B.
hasTollVariant
Indicates that an entity has a version or instance that requires paying a toll or fee for use or access.
-
C.
tollingType
Indicates the specific method or basis by which a toll, fee, or charge is applied or calculated in a given context.
-
D.
supportsElectronicTollCollection
Indicates that an entity is capable of handling or is compatible with electronic toll collection systems for automated toll payment.
-
E.
tollTagAccepted
Indicates that a particular toll tag is valid and can be used as payment at a given toll facility or system.
- 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_69f76ef0e8708190987c7254ed8c7abe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69fd974c0e8481909fdd312897c647b3 |
completed | May 8, 2026, 7:57 a.m. |
Created at: May 3, 2026, 4:20 p.m.