Triple

T22929125
Position Surface form Disambiguated ID Type / Status
Subject County Route 500-series network E569386 entity
Predicate hasComponent P35 FINISHED
Object County Route 533 (New Jersey) NE NERFINISHED

How this triple was built (3 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: County Route 533 (New Jersey) | Statement: [County Route 500-series network, hasComponent, County Route 533 (New Jersey)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: County Route 533 (New Jersey)
Context triple: [County Route 500-series network, hasComponent, County Route 533 (New Jersey)]
  • A. County Route 530 (New Jersey)
    County Route 530 (New Jersey) is an east–west county highway in southern New Jersey that runs through Burlington and Ocean counties, connecting several communities and major roadways.
  • B. County Route 531 (New Jersey)
    County Route 531 (New Jersey) is a north–south county highway in New Jersey that runs through Union and Essex counties, connecting several suburban communities and major roadways.
  • C. County Route 536 (New Jersey)
    County Route 536 in New Jersey is a county highway that runs across several South Jersey communities, serving as an important east–west connector in the regional road network.
  • D. County Route 532 (New Jersey)
    County Route 532 (New Jersey) is an east–west county highway in the New Jersey Pine Barrens, connecting several rural communities and major routes across Burlington and Ocean counties.
  • E. County Route 503 (New Jersey)
    County Route 503 (New Jersey) is a major north–south county highway in northeastern New Jersey that connects several communities in Bergen and Hudson counties and serves as an important local arterial route.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: County Route 533 (New Jersey)
Target entity description: County Route 533 (New Jersey) is a major north–south county highway running through central New Jersey, connecting several municipalities and serving as an important regional thoroughfare.
  • A. County Route 530 (New Jersey)
    County Route 530 (New Jersey) is an east–west county highway in southern New Jersey that runs through Burlington and Ocean counties, connecting several communities and major roadways.
  • B. County Route 531 (New Jersey)
    County Route 531 (New Jersey) is a north–south county highway in New Jersey that runs through Union and Essex counties, connecting several suburban communities and major roadways.
  • C. County Route 536 (New Jersey)
    County Route 536 in New Jersey is a county highway that runs across several South Jersey communities, serving as an important east–west connector in the regional road network.
  • D. County Route 532 (New Jersey)
    County Route 532 (New Jersey) is an east–west county highway in the New Jersey Pine Barrens, connecting several rural communities and major routes across Burlington and Ocean counties.
  • E. County Route 503 (New Jersey)
    County Route 503 (New Jersey) is a major north–south county highway in northeastern New Jersey that connects several communities in Bergen and Hudson counties and serves as an important local arterial route.
  • F. None of above. chosen

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_69e2458f7d008190901dccbaebeaba24 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f180dc33e8819099e5ad87207de57f completed April 29, 2026, 3:54 a.m.
Created at: April 17, 2026, 3:44 p.m.