Triple
T33864889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monte Isola |
E868020
|
entity |
| Predicate | hasRoadTrafficRestriction |
P29930
|
FINISHED |
| Object | no private cars for non-residents |
—
|
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: no private cars for non-residents | Statement: [Monte Isola, hasRoadTrafficRestriction, no private cars for non-residents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadTrafficRestriction Context triple: [Monte Isola, hasRoadTrafficRestriction, no private cars for non-residents]
-
A.
hasSpeedRestriction
Indicates that an entity is subject to a specified limit on its allowable speed.
-
B.
trafficRestriction
chosen
Indicates a limitation or prohibition on the movement or flow of traffic between entities, such as vehicles, routes, or areas.
-
C.
hasCarriagewayRestrictions
Indicates that certain limitations or prohibitions apply to the use or access of a specific carriageway.
-
D.
hasSpeedRestrictionReason
Indicates the reason or cause for which a speed restriction has been imposed on an entity.
-
E.
isTrafficCalmed
Indicates that a road or street has measures in place to reduce vehicle speed and improve safety for users.
- 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_69f34995029081909ede0f7df73d1a5e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe189fec148190aeef51b417ba15b0 |
completed | May 8, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69fe17285b0881908de7569d8dbd20bd |
completed | May 8, 2026, 5:02 p.m. |
Created at: May 1, 2026, 1:47 a.m.