Triple

T34161635
Position Surface form Disambiguated ID Type / Status
Subject Eikthyrnir E876290 entity
Predicate feedsWatersThatReach P178691 FINISHED
Object many rivers 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: many rivers | Statement: [Eikthyrnir, feedsWatersThatReach, many rivers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: feedsWatersThatReach
Context triple: [Eikthyrnir, feedsWatersThatReach, many rivers]
  • A. hasHeadwatersOf
    Indicates that a specified location or feature is the source or origin point of a particular river or watercourse.
  • B. isWatercourseOf
    Indicates that a watercourse (such as a river or stream) flows through, belongs to, or is geographically associated with a particular area or feature.
  • C. receivesFreshwaterFrom
    Indicates that one entity is supplied with or obtains freshwater from another entity as its source.
  • D. hasBodyOfWaterDrainedBy
    Indicates that a body of water is emptied or its water flow is carried away by a specified draining feature, such as a river, channel, or drainage system.
  • E. tributarySystem
    Indicates a relationship where one political entity pays regular tribute or offers deference to another, acknowledging the latter’s superior authority or status.
  • 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_69f349ac987481908a8e6053f665bc8b completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f713bfdc148190a249a7874320bab8 completed May 3, 2026, 9:22 a.m.
PD Predicate disambiguation batch_69f7127884388190884f23d181a65d19 completed May 3, 2026, 9:16 a.m.
PDg Predicate description generation batch_69f7135fa2988190a20a94cfe616d754 completed May 3, 2026, 9:20 a.m.
Created at: May 1, 2026, 1:54 a.m.