Triple

T181644
Position Surface form Disambiguated ID Type / Status
Subject Georgia State Route System E3888 entity
Predicate hasLegalDefinition P125 FINISHED
Object Georgia Code transportation statutes 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: Georgia Code transportation statutes | Statement: [Georgia State Route System, hasLegalDefinition, Georgia Code transportation statutes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLegalDefinition
Context triple: [Georgia State Route System, hasLegalDefinition, Georgia Code transportation statutes]
  • A. hasLegalStatus
    Indicates that an entity possesses a particular legal classification, recognition, or standing under law.
  • B. usesLegalCode
    Indicates that one entity applies, references, or operates under a particular legal code in its actions or regulations.
  • C. hasLegalIssue
    Indicates that an entity is involved in, associated with, or subject to a legal problem, dispute, or proceeding.
  • D. legalBasis chosen
    Indicates the legal rule, authority, or justification under which an action, decision, or status is established or carried out.
  • E. legalDoctrine
    Indicates that one legal principle, rule, or theory is being applied, referenced, or relied upon as an authoritative basis for interpreting or deciding a legal issue.
  • 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.