Triple

T27832539
Position Surface form Disambiguated ID Type / Status
Subject U.S. Route 95 in Oregon E703141 entity
Predicate isRemoteSegmentOf P124730 FINISHED
Object U.S. Route 95 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: U.S. Route 95 | Statement: [U.S. Route 95 in Oregon, isRemoteSegmentOf, U.S. Route 95]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isRemoteSegmentOf
Context triple: [U.S. Route 95 in Oregon, isRemoteSegmentOf, U.S. Route 95]
  • A. isRemoteInParts
    Indicates that the relationship or action occurs only in certain segments or portions of a larger whole, rather than being uniformly present throughout.
  • B. isSpaceSegmentOf chosen
    Indicates that one spatial region or segment is a constituent part or subdivision of a larger spatial extent or segment.
  • C. isSubsegmentOf
    Indicates that one segment is entirely contained within and forms a continuous part of another, larger segment.
  • D. isShortestStateSegmentOf
    Indicates that one state segment is the minimal-length segment among all segments that could represent that same portion of a state or process.
  • E. hasSegmentFrom
    Indicates that something includes or contains a segment that originates from or is derived from another specified source.
  • 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_69ef840b94b08190950a4f77296938b2 completed April 27, 2026, 3:43 p.m.
NER Named-entity recognition batch_69f6389cf96c8190a045e3c53f83f3cd completed May 2, 2026, 5:47 p.m.
PD Predicate disambiguation batch_69f6318ae6f08190b3f85f9201046a15 completed May 2, 2026, 5:16 p.m.
Created at: April 27, 2026, 5:57 p.m.