Triple

T6939286
Position Surface form Disambiguated ID Type / Status
Subject Noether charge E160630 entity
Predicate mayFailToBeConservedIf P74408 FINISHED
Object symmetry is anomalous 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: symmetry is anomalous | Statement: [Noether charge, mayFailToBeConservedIf, symmetry is anomalous]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mayFailToBeConservedIf
Context triple: [Noether charge, mayFailToBeConservedIf, symmetry is anomalous]
  • A. hasConservedQuantity
    Indicates that a system or process possesses a quantity that remains constant (is conserved) throughout its evolution or interactions.
  • B. mayDifferFrom
    Indicates that one entity is allowed or expected to be different from another entity, without requiring them to be identical.
  • C. mayResultIn
    Indicates that one entity has the potential to cause, lead to, or bring about another entity or outcome, without guaranteeing that it will occur.
  • D. mayHold
    Indicates that one entity is permitted or allowed to possess, contain, or maintain another entity.
  • E. hasConservationFunction
    Indicates that an entity serves a role or performs activities aimed at preserving, protecting, or maintaining the condition of another entity or resource.
  • 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_69c6884f3db4819080ad65da69386206 completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6e0c74fe48190aeaa018631e52ef6 completed March 27, 2026, 7:55 p.m.
PD Predicate disambiguation batch_69c6d7bd5a388190a57a96d925696ff6 completed March 27, 2026, 7:17 p.m.
PDg Predicate description generation batch_69c6e0c620f0819080e0ec49b36d4c30 completed March 27, 2026, 7:55 p.m.
Created at: March 27, 2026, 2:28 p.m.