Triple
T2284948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meishin Expressway |
E51366
|
entity |
| Predicate | electronicTollCollection |
P395
|
FINISHED |
| Object | ETC |
—
|
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: ETC | Statement: [Meishin Expressway, electronicTollCollection, ETC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electronicTollCollection Context triple: [Meishin Expressway, electronicTollCollection, ETC]
-
A.
tollingType
Indicates the specific method or basis by which a toll, fee, or charge is applied or calculated in a given context.
-
B.
isTollFacilityOf
Indicates that a facility (such as a toll booth, plaza, or gantry) is part of, or used to collect tolls for, a specific toll road or toll transportation infrastructure.
-
C.
fareSystem
chosen
Indicates a relationship where a system is used to determine, collect, or manage fares or payments for transportation or similar services.
-
D.
tollCollectionEnded
Indicates that the process of collecting tolls for a particular road, segment, or facility has been stopped or has come to an end.
-
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_69a88b08e4308190bdac9aebcca1c91a |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc245dd208190b13c5f5d05aa6990 |
completed | March 7, 2026, 6:14 a.m. |
| PD | Predicate disambiguation | batch_69abbdbb9e4c819085fc588626ec7c09 |
completed | March 7, 2026, 5:55 a.m. |
Created at: March 4, 2026, 7:48 p.m.