Triple

T12660712
Position Surface form Disambiguated ID Type / Status
Subject Silver Street E302414 entity
Predicate hasVehicleRestrictions P33452 FINISHED
Object yes 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: yes | Statement: [Silver Street, hasVehicleRestrictions, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasVehicleRestrictions
Context triple: [Silver Street, hasVehicleRestrictions, yes]
  • A. hasLimitedRoadAccess
    Indicates that an entity can only be reached by a small number of roads, restricted routes, or otherwise constrained vehicular access.
  • B. hasSpeedRestriction
    Indicates that an entity is subject to a specified limit on its allowable speed.
  • C. transportRestriction chosen
    Indicates that there are limitations, prohibitions, or special conditions governing the use of a particular mode or means of transportation between entities.
  • D. hasPrimaryVehicularAccessTo
    Indicates that one location or entity serves as the main route or means by which vehicles can reach or enter another location or entity.
  • E. hasDrivingConditions
    Indicates that a particular route, area, or time period is associated with specific driving conditions (such as weather, traffic, or road surface state) that affect how vehicles can be driven.
  • 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_69d7bded71a88190bb76e2413af9ea66 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d9617b07ec8190b714f04ae6654060 completed April 10, 2026, 8:45 p.m.
PD Predicate disambiguation batch_69d960b78ce8819091f15dd5013e6da5 completed April 10, 2026, 8:42 p.m.
Created at: April 9, 2026, 5:19 p.m.