Triple

T10223313
Position Surface form Disambiguated ID Type / Status
Subject Mancherial district E242635 entity
Predicate highwayConnectivity P385 FINISHED
Object connected by national and state highways 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: connected by national and state highways | Statement: [Mancherial district, highwayConnectivity, connected by national and state highways]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: highwayConnectivity
Context triple: [Mancherial district, highwayConnectivity, connected by national and state highways]
  • A. nationalHighwayConnectivity
    Indicates the extent to which locations are linked by a network of national highways enabling direct or efficient road travel between them.
  • B. connectsToHighway
    Indicates that one location, road, or route has a direct access point or linkage to a highway.
  • C. motorwayServedBy
    Indicates that a motorway is connected to or accessed by a particular service facility, route, or transport service.
  • D. hasMajorHighway chosen
    Indicates that a location or area is served by or directly connected to a major highway route.
  • E. isIntercityHighway
    Indicates that a given road segment functions as a highway connecting different cities or urban areas.
  • 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_69d381ae26c48190985abd0e25ee5d04 completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d3aa8305e481908ee1fc1d9eda6fa0 completed April 6, 2026, 12:43 p.m.
PD Predicate disambiguation batch_69d3955f61f88190b8d37ff645cd44d3 completed April 6, 2026, 11:13 a.m.
Created at: April 6, 2026, 11:10 a.m.