Triple
T5681571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | helium-3 |
E125209
|
entity |
| Predicate | magneticMoment |
P7807
|
FINISHED |
| Object | nuclear magnetic moment used in NMR |
—
|
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: nuclear magnetic moment used in NMR | Statement: [helium-3, magneticMoment, nuclear magnetic moment used in NMR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: magneticMoment Context triple: [helium-3, magneticMoment, nuclear magnetic moment used in NMR]
-
A.
hasMagneticMoment
chosen
Indicates that an entity possesses a magnetic moment, characterizing the strength and orientation of its magnetism.
-
B.
magneticField
Indicates the presence, strength, or configuration of a magnetic field associated with an entity or region.
-
C.
magneticFieldStrength
Indicates the intensity or magnitude of a magnetic field associated with an entity or at a specific location.
-
D.
magneticFieldCharacteristic
Indicates a relationship where a magnetic field is associated with or exhibits a specific characteristic or property.
-
E.
usesMagnetType
Indicates that one entity employs or operates with a specific type of magnet in its function or configuration.
- 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_69c0082a884c8190a79001bae658941f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0248751bc8190b12aaa42d1ef17e3 |
completed | March 22, 2026, 5:19 p.m. |
| PD | Predicate disambiguation | batch_69c021be59088190a81c880957f666ab |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:44 p.m.