Triple

T26555174
Position Surface form Disambiguated ID Type / Status
Subject Glacial Lake Iroquois E671787 entity
Predicate hadOutlet P48330 FINISHED
Object Hudson River valley 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: Hudson River valley | Statement: [Glacial Lake Iroquois, hadOutlet, Hudson River valley]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hadOutlet
Context triple: [Glacial Lake Iroquois, hadOutlet, Hudson River valley]
  • A. hasOutlet chosen
    Indicates that one entity provides, contains, or is equipped with an outlet or point of access for another entity.
  • B. locatedAtOutletOf
    Indicates that one entity is positioned at or directly adjacent to the outlet or discharge point of another entity (such as a flow, channel, or system).
  • C. hasOutletWorks
    Indicates that an entity has associated works (such as publications, products, or content) that are distributed, presented, or made available through a particular outlet or channel.
  • D. hadBranchIn
    Indicates that an organization or entity maintained a branch, office, or subsidiary located in another specified place or entity.
  • E. doesNotHaveOutletTo
    Indicates that one entity lacks any direct outlet, passage, or connection leading to another entity or to an external space.
  • 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_69eeb32163f08190af5f81282738e27a completed April 27, 2026, 12:51 a.m.
NER Named-entity recognition batch_69f614661bc08190bd533fbfac7da9fe completed May 2, 2026, 3:12 p.m.
PD Predicate disambiguation batch_69f602d7b1b0819095ddd3b5169f8ce2 completed May 2, 2026, 1:57 p.m.
Created at: April 27, 2026, 1:49 a.m.