Triple

T14582561
Position Surface form Disambiguated ID Type / Status
Subject U.S. Route 169 E342227 entity
Predicate hasBusinessRoutes P114947 FINISHED
Object in selected communities 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: in selected communities | Statement: [U.S. Route 169, hasBusinessRoutes, in selected communities]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasBusinessRoutes
Context triple: [U.S. Route 169, hasBusinessRoutes, in selected communities]
  • A. hasBusinessRoute
    Indicates that there exists an established commercial or service route connecting two business-related entities.
  • B. isBusinessRoute
    Indicates that a route functions primarily for business-related travel or commercial purposes between locations.
  • C. isMajorBusinessRoute
    Indicates that a route serves as a primary corridor for significant commercial or business-related traffic and activities.
  • D. hasBusinessTypeAlong
    Indicates that a business or commercial entity located along a route, corridor, or area is associated with a specific type or category of business activity.
  • E. hasBusinessNode
    Indicates that an entity is associated with, linked to, or represented by a specific business-related node within a business structure or network.
  • F. None of above. chosen

Provenance (4 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_69d822ddc0f081909cd8163c7de298cd completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb41e71748190a1deacc819dd26d3 completed April 14, 2026, 9:39 p.m.
PD Predicate disambiguation batch_69de656a953481909a4645b004c40de7 completed April 14, 2026, 4:03 p.m.
PDg Predicate description generation batch_69de716c17cc8190aeb85296abee85a7 completed April 14, 2026, 4:55 p.m.
Created at: April 10, 2026, 1:24 a.m.