Triple

T19633145
Position Surface form Disambiguated ID Type / Status
Subject State Road 39 E471320 entity
Predicate abbreviation P43 FINISHED
Object SR 39 NE NERFINISHED

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: SR 39 | Statement: [State Road 39, abbreviation, SR 39]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SR 39
Context triple: [State Road 39, abbreviation, SR 39]
  • A. SR 39 chosen
    SR 39 is a state highway in Georgia that runs generally north–south through the southwestern part of the state, connecting several small towns and rural areas.
  • B. SR 390
    SR 390 is a state highway in Florida that serves as a key east–west route in the Panama City area, connecting residential, commercial, and coastal regions.
  • C. SR 33
    SR 33 is a north–south California state highway that runs from Ventura through the Transverse Ranges and Central Valley, serving both coastal and inland communities.
  • D. SR 37
    SR 37 is a state highway in Northern California that runs along the northern edge of San Pablo Bay, connecting U.S. Route 101 in Marin County to Interstate 80 in Solano County.
  • E. SR 37
    SR 37 is a state highway in Ohio that runs east–west across the central part of the state, connecting several communities and intersecting multiple major routes.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e511f28481909f4bc3ea9191e54a completed April 10, 2026, 11:54 a.m.
NER Named-entity recognition batch_69e6410449ec8190b8c20c0e09cd9156 completed April 20, 2026, 3:06 p.m.
Created at: April 10, 2026, 1:44 p.m.