Triple

T30840474
Position Surface form Disambiguated ID Type / Status
Subject San Diego County highway system E785493 entity
Predicate roadJurisdiction P101826 FINISHED
Object county 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: county | Statement: [San Diego County highway system, roadJurisdiction, county]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: roadJurisdiction
Context triple: [San Diego County highway system, roadJurisdiction, county]
  • A. roadNetworkJurisdiction chosen
    Indicates the authority or entity responsible for managing, regulating, or maintaining a given segment of the road network.
  • B. roadTrafficRuleJurisdiction
    Indicates the jurisdiction or authority under whose road traffic rules a given situation, entity, or action is governed.
  • C. governmentJurisdiction
    Indicates the governmental body or authority that has legal power, control, or regulatory oversight over a given entity or activity.
  • D. legalJurisdiction
    Indicates the legal authority or geographic area whose laws and courts have the power to govern, regulate, or adjudicate matters involving the related entities.
  • E. managementJurisdiction
    Indicates that one entity has formal authority or responsibility to manage, oversee, or administer another entity or domain within a defined scope or area.
  • 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_69f224b73d8c81908129383bfb397c87 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f69142ca9c8190b56b7fa1321f8867 completed May 3, 2026, 12:05 a.m.
PD Predicate disambiguation batch_69f68b7d2794819092fef8a63f4f3de8 completed May 2, 2026, 11:40 p.m.
Created at: April 29, 2026, 8:45 p.m.