Triple
T33117558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A67 motorway (Germany) |
E847497
|
entity |
| Predicate | isTollFreeFor |
P50895
|
FINISHED |
| Object | passenger cars |
—
|
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: passenger cars | Statement: [A67 motorway (Germany), isTollFreeFor, passenger cars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTollFreeFor Context triple: [A67 motorway (Germany), isTollFreeFor, passenger cars]
-
A.
hasTollFreeSection
chosen
Indicates that a route, road, or transportation facility includes at least one segment where no toll is charged for use.
-
B.
tollFreeBridgedWith
Indicates that a toll-free communication channel is connected or linked via a bridging mechanism to another network, system, or call path.
-
C.
tollFreeBridgedTo
Indicates that a toll-free number is connected or forwarded to another destination number or endpoint.
-
D.
tollFreePrefixExample
Indicates that the subject is an example of a telephone number prefix that designates a toll-free calling number.
-
E.
tollFreeForMostSections
Indicates that the majority of sections within something (such as a route, service, or facility) can be used without paying a toll.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d716064c8190bf355a040ac09ab6 |
completed | May 3, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69f6d27224708190b31a541cebe0ff77 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:27 a.m.