Triple
T7489941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Planck energy |
E176979
|
entity |
| Predicate | hasOrderOfMagnitudeInElectronvolts |
P76544
|
FINISHED |
| Object | 10^28 eV |
—
|
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: 10^28 eV | Statement: [Planck energy, hasOrderOfMagnitudeInElectronvolts, 10^28 eV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrderOfMagnitudeInElectronvolts Context triple: [Planck energy, hasOrderOfMagnitudeInElectronvolts, 10^28 eV]
-
A.
hasRestEnergy
Indicates that an entity possesses intrinsic energy associated with its mass when at rest, independent of its motion or external forces.
-
B.
dimensionOfEnergy
Indicates a relationship where a specified dimension or unit is associated with a particular measure or quantity of energy.
-
C.
maximumProtonEnergy
Indicates the highest energy value that protons can attain in a given system, process, or context.
-
D.
beamEnergyUnit
Indicates the unit of measurement used to express the energy of a beam.
-
E.
typicalEnergyRange
Indicates the usual or characteristic range of energy values associated with an entity, process, or interaction.
- 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_69c69f2583808190bd1a4936c42a5815 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f55bdb3481908653b46eafba011d |
completed | March 27, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c6f03eeaa88190a5215772ed05ee9f |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f105e320819091db3cdb1f1351f0 |
completed | March 27, 2026, 9:05 p.m. |
Created at: March 27, 2026, 3:43 p.m.