Triple

T1066538
Position Surface form Disambiguated ID Type / Status
Subject Georgia State Route 1 E23222 entity
Predicate routeFunction P24286 FINISHED
Object major north–south corridor in western Georgia 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: major north–south corridor in western Georgia | Statement: [Georgia State Route 1, routeFunction, major north–south corridor in western Georgia]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: routeFunction
Context triple: [Georgia State Route 1, routeFunction, major north–south corridor in western Georgia]
  • A. route
    Indicates that one entity serves as a path or course used to travel or move between locations associated with another entity.
  • B. routeFamily
    Indicates a familial or hierarchical relationship between routes, such as one route being derived from, grouped with, or subordinate to another within a routing structure.
  • C. routeVia
    Indicates that a connection, path, or communication between two points is established or carried out through an intermediate location, node, or channel.
  • D. routeEndRegion
    Indicates the geographic region where a route terminates or reaches its endpoint.
  • E. routeDescription
    Indicates a textual explanation or summary of the path, course, or itinerary taken between 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_69a493ee1f908190992b5f0d1b04459b completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4b9e1047481909af1cf8df2a01fff completed March 1, 2026, 10:12 p.m.
PD Predicate disambiguation batch_69a4b736f1e881909bace735b38c0ade completed March 1, 2026, 10:01 p.m.
PDg Predicate description generation batch_69a4b9df0a308190a0d87dcd8afe58bc completed March 1, 2026, 10:12 p.m.
Created at: March 1, 2026, 7:42 p.m.