Triple

T181651
Position Surface form Disambiguated ID Type / Status
Subject Georgia State Route System E3888 entity
Predicate hasJurisdictionLevel P3734 FINISHED
Object state 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: state | Statement: [Georgia State Route System, hasJurisdictionLevel, state]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasJurisdictionLevel
Context triple: [Georgia State Route System, hasJurisdictionLevel, state]
  • A. hasJurisdictionOver
    Indicates that one authority or governing body holds legal power or control to make and enforce decisions over another entity, area, or matter.
  • B. typeOfJurisdiction chosen
    Indicates the specific kind or category of legal authority or control that one jurisdiction holds in relation to a given legal or administrative context.
  • C. hasOriginalJurisdictionOver
    Indicates that a legal body or authority has the power to hear and decide a case first, before any appellate review by higher bodies.
  • D. hasLevel
    Indicates that an entity possesses or is associated with a particular degree, rank, or stage within an ordered scale or hierarchy.
  • E. hasDivisionLevel
    Indicates that one entity is associated with a specific hierarchical or organizational division level of another entity.
  • 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_69a25497e2f08190a040f8c6e1842643 completed Feb. 28, 2026, 2:36 a.m.
NER Named-entity recognition batch_69a25923507c8190bd7f6eda404b0da0 completed Feb. 28, 2026, 2:55 a.m.
PD Predicate disambiguation batch_69a2566ccc288190add5624ede96d82b completed Feb. 28, 2026, 2:43 a.m.
Created at: Feb. 28, 2026, 2:40 a.m.