Triple
T9564544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Planck volume |
E230756
|
entity |
| Predicate | approximateVolumeInCubicCentimetres |
P89817
|
FINISHED |
| Object | approximately 4.22×10^-99 cm^3 |
—
|
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: approximately 4.22×10^-99 cm^3 | Statement: [Planck volume, approximateVolumeInCubicCentimetres, approximately 4.22×10^-99 cm^3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateVolumeInCubicCentimetres Context triple: [Planck volume, approximateVolumeInCubicCentimetres, approximately 4.22×10^-99 cm^3]
-
A.
approximateWeightInPounds
Indicates the estimated weight of an entity expressed in pounds, rather than an exact measured value.
-
B.
hasDimensionsApprox
Indicates that an entity has physical dimensions that are known only approximately, rather than as exact measurements.
-
C.
approximateMass
Indicates that one entity has a mass value that is an estimate or close approximation of the mass of another entity.
-
D.
approximateDiameter
Indicates that one entity specifies the estimated or rough measurement of another entity’s diameter.
-
E.
approximateLengthInMeters
Indicates the estimated or roughly measured length of something expressed in meters.
- 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_69ca847e53a88190a60eed7e02257f10 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd996a01b081908e2782f41520f73d |
completed | April 1, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69ccd594d0ac8190a81bc11a3a538167 |
completed | April 1, 2026, 8:21 a.m. |
| PDg | Predicate description generation | batch_69ccd93e90048190a2b0d7c5c195ba98 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:04 p.m.