Triple

T18815796
Position Surface form Disambiguated ID Type / Status
Subject neutron E460130 entity
Predicate magneticMomentValue P7807 FINISHED
Object approximately −1.913 nuclear magnetons 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 −1.913 nuclear magnetons | Statement: [neutron, magneticMomentValue, approximately −1.913 nuclear magnetons]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: magneticMomentValue
Context triple: [neutron, magneticMomentValue, approximately −1.913 nuclear magnetons]
  • A. hasMagneticMoment chosen
    Indicates that an entity possesses a magnetic moment, characterizing the strength and orientation of its magnetism.
  • B. magneticFieldStrength
    Indicates the intensity or magnitude of a magnetic field associated with an entity or at a specific location.
  • C. magneticField
    Indicates the presence, strength, or configuration of a magnetic field associated with an entity or region.
  • D. nuclearMagneticMomentSign
    Indicates whether the direction of an entity’s nuclear magnetic moment is positive or negative relative to a chosen reference or external field.
  • E. magneticCharge
    Indicates that an entity possesses a specified magnetic charge or is associated with a particular quantity or type of magnetic charge.
  • 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_69d8d398c7d4819091cb2f7e48948aeb completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e5a3e092e081908fc310c70f646e79 completed April 20, 2026, 3:56 a.m.
PD Predicate disambiguation batch_69e48d1b10ec8190985c6fb5766ff981 completed April 19, 2026, 8:06 a.m.
Created at: April 10, 2026, 11:53 a.m.