Triple

T1536900
Position Surface form Disambiguated ID Type / Status
Subject Menominee River E32569 entity
Predicate hasWatershedCharacteristic P29610 FINISHED
Object heavily forested 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: heavily forested | Statement: [Menominee River, hasWatershedCharacteristic, heavily forested]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasWatershedCharacteristic
Context triple: [Menominee River, hasWatershedCharacteristic, heavily forested]
  • A. hasWatershed
    Indicates that one geographic area or feature is part of, drains into, or is hydrologically defined by a particular watershed.
  • B. hydrologicalCharacteristic
    Indicates a relationship where a hydrological feature or condition (such as water flow, level, or behavior) characterizes or describes another entity.
  • C. hasWatercourseType
    Indicates the specific kind or category of watercourse (such as river, stream, or canal) associated with an entity.
  • D. hasWatershedUse
    Indicates that a particular type of use, activity, or function is associated with or applied to a watershed.
  • E. hasHydrologicalFunction
    Indicates that something performs a role or action related to the movement, storage, or regulation of water within a hydrological system.
  • 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_69a885ea86308190998f6bc14bb91f8e completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a915f323bc8190aa757142c225e0ae completed March 5, 2026, 5:34 a.m.
PD Predicate disambiguation batch_69a907b046448190be8ea4d7b20255f7 completed March 5, 2026, 4:33 a.m.
PDg Predicate description generation batch_69a915f1694081908f87b509eda1309f completed March 5, 2026, 5:34 a.m.
Created at: March 4, 2026, 7:26 p.m.