Triple

T34471792
Position Surface form Disambiguated ID Type / Status
Subject Nisnevich topology E884926 entity
Predicate baseChangeBehavior P178984 FINISHED
Object stable under base change of schemes 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: stable under base change of schemes | Statement: [Nisnevich topology, baseChangeBehavior, stable under base change of schemes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: baseChangeBehavior
Context triple: [Nisnevich topology, baseChangeBehavior, stable under base change of schemes]
  • A. replacedBehavior
    Indicates that one behavior has been substituted or superseded by another behavior.
  • B. targetBehaviorChange
    Indicates a relationship where an intervention or influence is intended to alter, modify, or redirect an entity’s behavior from its current state to a desired new state.
  • C. updatesProtocolBehaviorOf
    Indicates that one entity modifies or changes the protocol behavior or operational rules of another entity.
  • D. defaultBehavior
    Indicates the standard or fallback way an entity acts or responds when no specific or overriding instructions or conditions are provided.
  • E. changeType
    Indicates the specific kind or category of modification that has occurred to an entity or relationship.
  • 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_69f349c880408190ade571c471ab154a completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f719cc31ec819099bebcf833b14d76 completed May 3, 2026, 9:47 a.m.
PD Predicate disambiguation batch_69f71824431081908d9685d2462ea242 completed May 3, 2026, 9:40 a.m.
PDg Predicate description generation batch_69f719458378819081725f544efb1173 completed May 3, 2026, 9:45 a.m.
Created at: May 1, 2026, 2:01 a.m.