Triple

T1390269
Position Surface form Disambiguated ID Type / Status
Subject Higgs field E29938 entity
Predicate hasVacuumExpectationValue P9773 FINISHED
Object approximately 246 GeV 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: approximately 246 GeV | Statement: [Higgs field, hasVacuumExpectationValue, approximately 246 GeV]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasVacuumExpectationValue
Context triple: [Higgs field, hasVacuumExpectationValue, approximately 246 GeV]
  • A. isVacuumSolution
    Indicates that a spacetime metric satisfies Einstein’s field equations in the absence of matter or non-gravitational energy (i.e., the stress-energy tensor is zero).
  • B. hasValue
    Indicates that an entity is associated with a specific numerical, textual, or otherwise defined value.
  • C. hasStabilityExpectation
    Indicates that one entity expects another entity to maintain a certain level or condition of stability over time.
  • D. isValuedFor
    Indicates that one entity is appreciated, esteemed, or considered important because of a particular quality, contribution, or characteristic it provides to another entity.
  • E. hasApproximateValue chosen
    Indicates that one entity’s value is close to, but not exactly equal to, the value of another entity within an acceptable margin of error.
  • 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_69a498dc92f8819094a1108f8ac90f43 completed March 1, 2026, 7:51 p.m.
NER Named-entity recognition batch_69a4c35e023c8190b45688796d90534b completed March 1, 2026, 10:53 p.m.
PD Predicate disambiguation batch_69a4beffcf808190ab4cd0271257ce63 completed March 1, 2026, 10:34 p.m.
Created at: March 1, 2026, 7:59 p.m.