Triple

T15618865
Position Surface form Disambiguated ID Type / Status
Subject State Route 132 E375490 entity
Predicate abbreviation P43 FINISHED
Object SR 132 E823385 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 132 | Statement: [State Route 132, abbreviation, SR 132]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: SR 132
Context triple: [State Route 132, abbreviation, SR 132]
  • A. SR 132 chosen
    SR 132 is a state highway in Maine that connects several small communities and links with other major regional routes.
  • B. SR 131
    SR 131 is a state highway in Maine that runs through Knox and Waldo counties, connecting several coastal and inland communities.
  • C. SR 131
    SR 131 is a short primary state highway in Virginia that serves as a connector route within the state's road network.
  • D. SR 133
    SR 133 is a state highway in Maine that connects several central Maine communities and serves as a regional north–south transportation route.
  • E. SR 113
    SR 113 is a state highway in northern Ohio that runs east–west through several counties, connecting rural areas with small towns and cities.
  • 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_69d85ccf2794819096cda4cbcb02d478 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04e997ce481909b2f10d25705fbc6 completed April 16, 2026, 2:51 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff5f3b643c819093230df6cfe440b9 completed May 9, 2026, 4:22 p.m.
Created at: April 10, 2026, 4:13 a.m.