Triple

T17845233
Position Surface form Disambiguated ID Type / Status
Subject Maine State Route 242 E445640 entity
Predicate abbreviation P43 FINISHED
Object SR 242 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 242 | Statement: [Maine State Route 242, abbreviation, SR 242]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SR 242
Context triple: [Maine State Route 242, abbreviation, SR 242]
  • A. SR 242 chosen
    SR 242 is a state highway designated as State Route 242 within a U.S. state’s numbered road network.
  • B. SR 241
    SR 241 is a toll highway in Orange County, California, that serves as part of the Foothill Transportation Corridor connecting inland communities to major regional freeways.
  • C. SR 24
    SR 24 is a Florida state highway that runs east–west, connecting the Gulf Coast near Cedar Key to Gainesville and other inland communities.
  • D. SR 24
    SR 24 is a major state highway in the San Francisco Bay Area that connects Oakland to Contra Costa County through the Caldecott Tunnel.
  • E. SR 24
    SR 24 is a state highway in Georgia that runs generally southeast–northwest, connecting several cities and rural areas across the state.
  • 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_69d8b9f26f18819089c9e43250bee6ae completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e48ffa4c648190a88a4b0733493d91 completed April 19, 2026, 8:19 a.m.
Created at: April 10, 2026, 10:16 a.m.