Triple

T17220377
Position Surface form Disambiguated ID Type / Status
Subject State Road 112 E417962 entity
Predicate hasLimitedAccessSection P99 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: [State Road 112, hasLimitedAccessSection, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLimitedAccessSection
Context triple: [State Road 112, hasLimitedAccessSection, yes]
  • A. hasAccessConstraint
    Indicates that there is a limiting condition or rule governing the ability to access or use a particular resource, service, or action.
  • B. accessRestrictedTo
    Indicates that access to a resource, location, or information is limited exclusively to a specified entity or group under defined conditions.
  • C. hasLimitedServiceType
    Indicates that an entity is associated with a service that is restricted in scope, availability, or functionality compared to full or standard service types.
  • D. hasLimitedAuthorityOver
    Indicates that one entity holds a constrained or partial power to direct, control, or make decisions about another entity, but not full or unrestricted authority.
  • E. hasLimitation chosen
    Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
  • 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_69d886d779488190b131369541c04e7d completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e42ddd52d4819098b51d55e063c8ab completed April 19, 2026, 1:20 a.m.
PD Predicate disambiguation batch_69e3831e354881908c5505ffd15c84e9 completed April 18, 2026, 1:11 p.m.
Created at: April 10, 2026, 5:38 a.m.