Triple

T19865656
Position Surface form Disambiguated ID Type / Status
Subject PA 51 E477382 entity
Predicate connectsTo P845 FINISHED
Object US 19 — 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: US 19 | Statement: [PA 51, connectsTo, US 19]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: US 19
Context triple: [PA 51, connectsTo, US 19]
  • A. US 19 chosen
    US 19 is a major north–south United States highway running from Florida to Pennsylvania, serving numerous cities and regions along the eastern part of the country.
  • B. US 9
    US 9 is a major north–south U.S. Highway running along the East Coast, primarily through New Jersey and New York, connecting urban, suburban, and coastal communities.
  • C. US 219
    US 219 is a north–south U.S. highway running through parts of New York, Pennsylvania, Maryland, and West Virginia, serving as a key regional route in the Appalachian region.
  • D. US 17
    US 17 is a major north–south U.S. highway running along the southeastern United States, connecting Florida with several Atlantic coastal states.
  • E. US 29
    US 29 is a major north–south U.S. Highway running through the eastern United States, connecting cities from Florida to Virginia and beyond.
  • 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_69d8e51e7d948190aedbcd6c30361c39 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e6589eb24081908715b683de1edc68 completed April 20, 2026, 4:47 p.m.
Created at: April 10, 2026, 1:51 p.m.