Triple

T462009
Position Surface form Disambiguated ID Type / Status
Subject Boltzmann constant E7358 entity
Predicate CODATAStatus P3927 FINISHED
Object fixed exact constant in SI 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: fixed exact constant in SI | Statement: [Boltzmann constant, CODATAStatus, fixed exact constant in SI]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: CODATAStatus
Context triple: [Boltzmann constant, CODATAStatus, fixed exact constant in SI]
  • A. CODATA2022StandardUncertainty
    Indicates the standard uncertainty value associated with a CODATA 2022 recommended physical constant or measurement result.
  • B. hasCODATAValue
    Indicates that an entity is associated with a value specified or standardized by CODATA (Committee on Data for Science and Technology).
  • C. canonicalStatus chosen
    Indicates the formal or official standing of an entity within an established authoritative or normative system.
  • D. standardizationStatus
    Indicates the current stage or condition of an entity in a formal standardization process (e.g., proposed, under review, approved, deprecated).
  • E. relativeStandardUncertainty
    Indicates the ratio of a measurement’s standard uncertainty to the measured value, expressing uncertainty relative to the magnitude of the quantity.
  • 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_69a2e7e5c5bc8190a1dc8178218fba40 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2efc09eac8190add4bb5823b53ba7 completed Feb. 28, 2026, 1:38 p.m.
PD Predicate disambiguation batch_69a2ede8eac081908dffade6a5e7950b completed Feb. 28, 2026, 1:30 p.m.
Created at: Feb. 28, 2026, 1:12 p.m.