Triple

T24763968
Position Surface form Disambiguated ID Type / Status
Subject Bronze E619527 entity
Predicate corrosionResistanceRelativeToIron P157106 FINISHED
Object higher 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: higher | Statement: [Bronze, corrosionResistanceRelativeToIron, higher]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: corrosionResistanceRelativeToIron
Context triple: [Bronze, corrosionResistanceRelativeToIron, higher]
  • A. isCorrosionResistantWhen
    Indicates that an entity remains resistant to corrosion under specified conditions or circumstances.
  • B. isCorrosionResistantInAir
    Indicates that an entity maintains its integrity and does not significantly corrode when exposed to air under specified conditions.
  • C. corrodesIn
    Indicates that a substance undergoes corrosive degradation when it is in contact with a specified environment or medium.
  • D. erosionResistance
    Indicates how strongly one entity can withstand or prevent being worn away, degraded, or removed by erosive forces caused by another entity or the environment.
  • E. typicalValueForSteel
    Indicates that a given value represents a standard or commonly expected value associated with steel under typical conditions.
  • 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_69e2fabbea94819092ed41348909622f completed April 18, 2026, 3:30 a.m.
NER Named-entity recognition batch_69f410a4591c81909f918efd84a1f6f6 completed May 1, 2026, 2:32 a.m.
PD Predicate disambiguation batch_69f40ef612c88190ab2f3f08d4a92018 completed May 1, 2026, 2:24 a.m.
PDg Predicate description generation batch_69f410a001788190a457e41f53aaf90c completed May 1, 2026, 2:32 a.m.
Created at: April 18, 2026, 4:28 a.m.