Triple
T7229936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Planck units |
E154875
|
entity |
| Predicate | PlanckTimeApproxValueSI |
P74388
|
FINISHED |
| Object | 5.391247×10⁻⁴⁴ second |
—
|
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: 5.391247×10⁻⁴⁴ second | Statement: [Planck units, PlanckTimeApproxValueSI, 5.391247×10⁻⁴⁴ second]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PlanckTimeApproxValueSI Context triple: [Planck units, PlanckTimeApproxValueSI, 5.391247×10⁻⁴⁴ second]
-
A.
naturalUnitsValue
Indicates that a quantity is expressed in natural units, specifying its value when fundamental physical constants are normalized (e.g., c = ħ = k_B = 1).
-
B.
baseUnitsTimeExponent
Indicates the exponent applied to the time dimension in the base units that define a derived physical quantity.
-
C.
timeScaleUnit
Indicates the unit of temporal measurement (such as seconds, minutes, or hours) used to express a given time scale.
-
D.
valueSI
chosen
Indicates that an entity has a quantitative value expressed in SI (International System of Units) units.
-
E.
SIUnit
Indicates that something is expressed or measured using a unit from the International System of Units (SI).
- 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_69c68811dd1c8190ac460bb39e64e1f0 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea0d9b6c8190a0b5f0ab8d5cca19 |
completed | March 27, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69c6e761b7fc8190857794d78af1b468 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:54 p.m.