Triple

T18321180
Position Surface form Disambiguated ID Type / Status
Subject Pennsylvania Route 3 E438881 entity
Predicate isSignedAs P9766 FINISHED
Object PA 3 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: PA 3 | Statement: [Pennsylvania Route 3, isSignedAs, PA 3]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: PA 3
Context triple: [Pennsylvania Route 3, isSignedAs, PA 3]
  • A. PA 3 chosen
    PA 3 is a state highway in Pennsylvania that runs between Philadelphia and West Chester, serving as a major arterial route through the western suburbs of Philadelphia.
  • B. PA 5
    PA 5 is a state highway in northwestern Pennsylvania that runs along the Lake Erie shoreline, serving as a key east–west route in the region.
  • C. PA 31
    PA 31 is a state highway in Pennsylvania that runs east–west across the southwestern part of the state, connecting rural communities and serving as a regional transportation route.
  • D. PA 332
    PA 332 is a state highway in Pennsylvania that runs through Bucks County, connecting several suburban communities northeast of Philadelphia.
  • E. PA 43
    PA 43 is a state highway in Pennsylvania that primarily serves as part of the Mon–Fayette Expressway, connecting communities in the southwestern part of 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_69d8b916a2d081909e249e4902f6aad9 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e50aa5a3508190a3025e71c11d79e2 completed April 19, 2026, 5:02 p.m.
Created at: April 10, 2026, 10:36 a.m.