Triple

T10301281
Position Surface form Disambiguated ID Type / Status
Subject Kentucky Route 1500 E241634 entity
Predicate servesLocalTraffic P92991 FINISHED
Object true 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: true | Statement: [Kentucky Route 1500, servesLocalTraffic, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: servesLocalTraffic
Context triple: [Kentucky Route 1500, servesLocalTraffic, true]
  • A. servesSeasonalTraffic
    Indicates that an entity provides service only during specific seasons or periods of the year, rather than year-round.
  • B. supportsTraffic
    Indicates that one entity is capable of handling, carrying, or accommodating the flow or volume of traffic associated with another entity.
  • C. servesPilgrimTrafficTo
    Indicates that a location or entity functions as a route, hub, or provider facilitating the movement or flow of pilgrim traffic to a specified destination.
  • D. handlesSignificantShareOfTrafficAt
    Indicates that an entity is responsible for managing or processing a substantial proportion of the traffic volume at a specified location or system.
  • E. regulatesTrafficBetween
    Indicates that one entity controls, manages, or directs the flow of traffic occurring between two other entities or locations.
  • 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_69d381aaafc08190af475ef58dc16aba completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4d2eefe8881908a672c4dca7657ca completed April 7, 2026, 9:48 a.m.
PD Predicate disambiguation batch_69d4d1f35e548190be3b4d92d65d2d20 completed April 7, 2026, 9:44 a.m.
PDg Predicate description generation batch_69d4d29d7cf08190acd70cee634c5cdb completed April 7, 2026, 9:47 a.m.
Created at: April 6, 2026, 11:44 a.m.