Triple

T37494319
Position Surface form Disambiguated ID Type / Status
Subject River Raisin – Upper Branch E931784 entity
Predicate isUpstreamSegmentOf P188396 FINISHED
Object River Raisin 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: River Raisin | Statement: [River Raisin – Upper Branch, isUpstreamSegmentOf, River Raisin]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isUpstreamSegmentOf
Context triple: [River Raisin – Upper Branch, isUpstreamSegmentOf, River Raisin]
  • A. isAlternateSegmentOf
    Indicates that one segment serves as an alternative or substitute to another segment, typically in a sequence, structure, or path.
  • B. isSubsegmentOf
    Indicates that one segment is entirely contained within and forms a continuous part of another, larger segment.
  • C. 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.
  • D. isSubtrackOf
    Indicates that one musical track is a component, version, or derivative nested within another primary track.
  • E. isUpstreamPlantOf
    Indicates that one plant facility is located or operates upstream in a process, flow, or network relative to another plant facility.
  • F. None of above. chosen

Provenance (4 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_69f76ec457a4819094eeb3aed9baac11 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fba68077788190b311e027435fcf87 completed May 6, 2026, 8:37 p.m.
PD Predicate disambiguation batch_69fba34c65ac8190b298f0f00d1dcc0e completed May 6, 2026, 8:23 p.m.
PDg Predicate description generation batch_69fba67f78348190ab160988e4698394 completed May 6, 2026, 8:37 p.m.
Created at: May 3, 2026, 4:17 p.m.