Triple
T16492803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Electron |
E400606
|
entity |
| Predicate | hasComptonWavelength |
P123737
|
FINISHED |
| Object | 2.426310×10^−12 m |
—
|
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: 2.426310×10^−12 m | Statement: [Electron, hasComptonWavelength, 2.426310×10^−12 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComptonWavelength Context triple: [Electron, hasComptonWavelength, 2.426310×10^−12 m]
-
A.
hasRestMass
Indicates that an entity possesses a non-zero invariant mass when measured in its own rest frame.
-
B.
hasRestEnergy
Indicates that an entity possesses intrinsic energy associated with its mass when at rest, independent of its motion or external forces.
-
C.
hasRestMassUpperBound
Indicates that there is a specified maximum possible value for the rest mass of an entity.
-
D.
hasRelativisticEffects
Indicates that the relationship or process involves velocities or gravitational fields high enough that relativistic (Einsteinian) corrections to classical physics become significant.
-
E.
hasObservationWavelength
Indicates the specific wavelength at which an observation or measurement is made or recorded.
- 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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e30cb648190a52cb32896c4ac5a |
completed | April 18, 2026, 7:09 a.m. |
| PD | Predicate disambiguation | batch_69e296902d6c8190884ddb612b8c5b36 |
completed | April 17, 2026, 8:22 p.m. |
| PDg | Predicate description generation | batch_69e2d7f97e548190a474691a152bd8e8 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:13 a.m.