Triple
T10376215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | electron neutrino |
E244513
|
entity |
| Predicate | hasRestMassUpperBound |
P93654
|
FINISHED |
| Object | less than 1 eV/c^2 (order of magnitude) |
—
|
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: less than 1 eV/c^2 (order of magnitude) | Statement: [electron neutrino, hasRestMassUpperBound, less than 1 eV/c^2 (order of magnitude)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRestMassUpperBound Context triple: [electron neutrino, hasRestMassUpperBound, less than 1 eV/c^2 (order of magnitude)]
-
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.
hasMassTerm
Indicates that one entity is classified as a mass (uncountable) term associated with another entity.
-
D.
hasMassScale
Indicates that an entity is associated with a particular mass measurement scale or system used to quantify its mass.
-
E.
hasMass_kg
Indicates that an entity possesses a specific mass measured in kilograms.
- 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_69d381b3e328819094b23b8edcd29b5a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e98278e08190a4d3ff88b4039e49 |
completed | April 7, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69d4dface5508190a7b42f01ad0a19a2 |
completed | April 7, 2026, 10:42 a.m. |
| PDg | Predicate description generation | batch_69d4e944fac4819093b0312aa0efd729 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, 12:02 p.m.