Triple

T24778569
Position Surface form Disambiguated ID Type / Status
Subject Lower Tunguska E619927 entity
Predicate confluenceWithYenisei P2416 FINISHED
Object downstream of Turukhansk LITERAL FINISHED

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: downstream of Turukhansk | Statement: [Lower Tunguska, confluenceWithYenisei, downstream of Turukhansk]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: confluenceWithYenisei
Context triple: [Lower Tunguska, confluenceWithYenisei, downstream of Turukhansk]
  • A. riverConfluence
    Indicates the location or relationship where two or more rivers or streams join and merge into a single watercourse.
  • B. isBelievedToBeConfluenceOf
    Indicates that something is regarded or considered to be the point where multiple elements, sources, or influences come together.
  • C. locatedAtConfluenceOf
    Indicates that something is situated at the meeting point where two or more bodies of water or similar flowing features join together.
  • D. confluenceWith chosen
    Indicates that one entity joins or merges together with another, typically at a shared meeting point.
  • E. isMajorWatercourseOf
    Indicates that a watercourse is a primary or significant river or stream associated with, or flowing through, a particular geographic area or feature.
  • 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_69e2fabdbe8c8190adbb9434b8636cad completed April 18, 2026, 3:30 a.m.
NER Named-entity recognition batch_69f42d9000b8819081ea2605f3c193d6 completed May 1, 2026, 4:35 a.m.
PD Predicate disambiguation batch_69f420f471a0819095a6cd24ed8f7476 completed May 1, 2026, 3:41 a.m.
Created at: April 18, 2026, 4:42 a.m.