Triple

T17341043
Position Surface form Disambiguated ID Type / Status
Subject Banach–Mazur distance E421065 entity
Predicate isScaleInvariant P127094 FINISHED
Object true 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: true | Statement: [Banach–Mazur distance, isScaleInvariant, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isScaleInvariant
Context triple: [Banach–Mazur distance, isScaleInvariant, true]
  • A. hasScale
    Indicates that one entity possesses or is characterized by a scale or graduated measurement system related to another entity.
  • B. scalesWith
    Indicates that a change in one quantity is systematically associated with a proportional or otherwise dependent change in another quantity.
  • C. hasScaleHeight
    Indicates the characteristic vertical distance over which a quantity (such as pressure, density, or concentration) decreases by a fixed factor in a stratified medium.
  • D. coversScale
    Indicates that one entity spans, includes, or applies across the full range or extent of another entity’s scale.
  • E. hasScaleParameter
    Indicates that an entity is associated with a scale parameter that controls the magnitude or dispersion of a related quantity or distribution.
  • 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_69d889d3adc881909319f1edb8d2a956 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e43a15f6488190ad7d489e7391ab12 completed April 19, 2026, 2:12 a.m.
PD Predicate disambiguation batch_69e3b021a5bc81909ae55406f9d0b37f completed April 18, 2026, 4:24 p.m.
PDg Predicate description generation batch_69e3b2a225b08190a50f984caa6513b9 completed April 18, 2026, 4:34 p.m.
Created at: April 10, 2026, 5:44 a.m.