Triple

T24616504
Position Surface form Disambiguated ID Type / Status
Subject Оленёк E609274 entity
Predicate имеетГидрологическийРежим P50263 FINISHED
Object половодье весной 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: половодье весной | Statement: [Оленёк, имеетГидрологическийРежим, половодье весной]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: имеетГидрологическийРежим
Context triple: [Оленёк, имеетГидрологическийРежим, половодье весной]
  • A. hasHydrologicalRegime chosen
    Indicates that one entity (typically a water body or hydrological system) is characterized by, or associated with, a particular pattern or regime of water flow and levels over time.
  • B. hasWatercourseType
    Indicates the specific kind or category of watercourse (such as river, stream, or canal) associated with an entity.
  • C. hasRiverineCharacteristic
    Indicates that something possesses qualities, features, or conditions associated with rivers or river environments.
  • D. hasWaterCharacteristics
    Indicates that one entity possesses qualities, properties, or behaviors characteristic of water.
  • 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.

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_69e2c4d1140081909c58667bf68f80c3 completed April 17, 2026, 11:40 p.m.
NER Named-entity recognition batch_69f2be044d4c819094e14eda28d371a7 completed April 30, 2026, 2:27 a.m.
PD Predicate disambiguation batch_69f2a6ca751c8190a040c10d701ecf3a completed April 30, 2026, 12:48 a.m.
Created at: April 18, 2026, 2:31 a.m.