Triple

T367836
Position Surface form Disambiguated ID Type / Status
Subject Kentucky Route 61 E8201 entity
Predicate servesRole P11687 FINISHED
Object link between small communities and larger routes in Kentucky 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: link between small communities and larger routes in Kentucky | Statement: [Kentucky Route 61, servesRole, link between small communities and larger routes in Kentucky]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: servesRole
Context triple: [Kentucky Route 61, servesRole, link between small communities and larger routes in Kentucky]
  • A. definesRole
    Indicates that one entity specifies or establishes the role, function, or position of another entity within a given context.
  • B. refersToRole
    Indicates that one entity designates, mentions, or points to another entity specifically in its capacity as a role or position.
  • C. roleInvolves
    Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
  • D. typeOfRole
    Indicates that one entity specifies the kind or category of role that another entity holds or performs.
  • E. servedByService
    Indicates that something is provided, handled, or fulfilled by a particular service.
  • 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_69a2e7f2ec648190b42bc7db424f8109 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2ebeab13c8190b15c2f10310ec6a8 completed Feb. 28, 2026, 1:21 p.m.
PD Predicate disambiguation batch_69a2e95ede588190998fdf3a6ea90498 completed Feb. 28, 2026, 1:10 p.m.
PDg Predicate description generation batch_69a2ea0b23ec8190bef9d593162388a4 completed Feb. 28, 2026, 1:13 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.