Triple

T5239040
Position Surface form Disambiguated ID Type / Status
Subject Russky Bridge E118293 entity
Predicate iceLoadResistance P20750 FINISHED
Object designed to withstand ice loads 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: designed to withstand ice loads | Statement: [Russky Bridge, iceLoadResistance, designed to withstand ice loads]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: iceLoadResistance
Context triple: [Russky Bridge, iceLoadResistance, designed to withstand ice loads]
  • A. iceStrengthened
    Indicates that an entity has been made stronger, reinforced, or enhanced through the application or influence of ice.
  • B. iceFeature
    Indicates a relationship where a geographic or environmental feature is composed of, covered by, or characterized by ice.
  • C. designedToWithstand chosen
    Indicates that something has been intentionally created or engineered to resist, endure, or remain functional under specified conditions, forces, or stresses.
  • D. typeOfResistance
    Indicates the kind or category of resistance that characterizes how an entity opposes, impedes, or withstands another entity or influence.
  • E. hasIceSurface
    Indicates that an entity possesses or is characterized by a surface composed primarily of ice.
  • 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_69bd4467db0881909b3b0982df32cc8f completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd7b290b88819095bc99c234260d25 completed March 20, 2026, 4:51 p.m.
PD Predicate disambiguation batch_69bd77c1397c8190a7fd844d7a396e54 completed March 20, 2026, 4:37 p.m.
Created at: March 20, 2026, 1:49 p.m.