Triple

T37044584
Position Surface form Disambiguated ID Type / Status
Subject Selfoss (waterfall) E916871 entity
Predicate positionRelativeToDettifoss P200970 FINISHED
Object upstream 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: upstream | Statement: [Selfoss (waterfall), positionRelativeToDettifoss, upstream]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: positionRelativeToDettifoss
Context triple: [Selfoss (waterfall), positionRelativeToDettifoss, upstream]
  • A. positionRelativeToReykjavík
    Indicates the spatial position or location of an entity in relation to the city of Reykjavík.
  • B. positionRelativeToSummit
    Indicates the spatial relationship of an entity’s location with respect to the summit of a feature or structure.
  • C. positionRelativeToPower
    Indicates the spatial or structural placement of one entity in relation to a power source, power line, or power-related infrastructure.
  • D. positionRelativeToUranium
    Indicates the spatial relationship or placement of an entity with respect to a reference point defined by uranium.
  • E. positionRelativeToNiagaraFalls
    Indicates the spatial relationship of an entity’s location with respect to Niagara Falls, such as its direction, distance, or relative placement.
  • 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_69f76e93ec4c8190be81cf87354d9155 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69ffbe9e47688190a2692566dc326646 completed May 9, 2026, 11:09 p.m.
PD Predicate disambiguation batch_69ffbb7b45388190b62cbde5c2d435cd completed May 9, 2026, 10:55 p.m.
PDg Predicate description generation batch_69ffbe9c7c348190b6b72455d6a3e3d8 completed May 9, 2026, 11:09 p.m.
Created at: May 3, 2026, 4:14 p.m.