Triple

T5465083
Position Surface form Disambiguated ID Type / Status
Subject Maine State Route 7 E122687 entity
Predicate abbreviation P43 FINISHED
Object SR 7 E270127 NE 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: SR 7 | Statement: [Maine State Route 7, abbreviation, SR 7]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SR 7
Context triple: [Maine State Route 7, abbreviation, SR 7]
  • A. SR 7 chosen
    SR 7 is a major east–west state highway in Virginia that connects the Washington, D.C. metropolitan area with communities in Northern Virginia and the Shenandoah Valley.
  • B. SR 57
    SR 57 is a state highway in Ohio that serves as a regional connector route through several communities in the northern part of the state.
  • C. SR 27
    SR 27 is a state highway in Maine that runs north–south, connecting coastal communities with inland towns and recreational areas.
  • D. SR 2
    SR 2 is a state highway in the Florida Panhandle that runs near the Alabama border, serving as an east–west route through rural communities.
  • E. SR 60
    SR 60 is a major east–west freeway in Southern California that connects Los Angeles to the Inland Empire and serves as a key commuter and freight corridor.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69bd4643f16081908d7f29e08096115a completed March 20, 2026, 1:06 p.m.
NER Named-entity recognition batch_69bd920590b481909b92091678ff1414 completed March 20, 2026, 6:29 p.m.
NED1 Entity disambiguation (via context triple) batch_69bf41524c3c81908425a02162496c15 completed March 22, 2026, 1:09 a.m.
Created at: March 20, 2026, 2:08 p.m.