Triple

T32793849
Position Surface form Disambiguated ID Type / Status
Subject U.S. Route 302 in Maine E838704 entity
Predicate westernTerminusAtStateLineWith P171966 FINISHED
Object New Hampshire 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: New Hampshire | Statement: [U.S. Route 302 in Maine, westernTerminusAtStateLineWith, New Hampshire]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: westernTerminusAtStateLineWith
Context triple: [U.S. Route 302 in Maine, westernTerminusAtStateLineWith, New Hampshire]
  • A. westernTerminusNear
    Indicates that the western endpoint of one entity is located close to another entity.
  • B. westernTerminusCrosses
    Indicates that the western endpoint of a route, line, or path intersects or passes over another feature or boundary.
  • C. westernTerminusConnectsTo
    Indicates that the western endpoint or terminus of one route, line, or path is directly connected to another specified route, line, or location.
  • D. westernTerminusDetail
    Indicates the specific endpoint location or characteristics associated with the western terminus of a route or linear feature.
  • E. westernTerminusAtBorderWith chosen
    Indicates that something’s western endpoint or final location lies at a border shared with another region or entity.
  • F. None of above.

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_69f3493c7f6881908edf2aa13631d1e0 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6ce6d659881909ddcec1d2966e020 completed May 3, 2026, 4:26 a.m.
PD Predicate disambiguation batch_69f6cc1667a48190b42684f6ec22dae9 completed May 3, 2026, 4:16 a.m.
Created at: May 1, 2026, 1:14 a.m.