Triple
T9564553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Planck volume |
E230756
|
entity |
| Predicate | hasLog10ValueInCubicMetres |
P89819
|
FINISHED |
| Object | approximately -104.375 |
—
|
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 -104.375 | Statement: [Planck volume, hasLog10ValueInCubicMetres, approximately -104.375]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLog10ValueInCubicMetres Context triple: [Planck volume, hasLog10ValueInCubicMetres, approximately -104.375]
-
A.
meanVolume_km3
Indicates the average volume of an entity, measured in cubic kilometers (km³), typically over a specified period or set of conditions.
-
B.
valueSI
Indicates that an entity has a quantitative value expressed in SI (International System of Units) units.
-
C.
excavatedVolume
Indicates the amount of material removed from a site or area as a result of an excavation activity.
-
D.
cabinVolumeCubicMeters
Indicates the volume of an enclosed cabin space measured in cubic meters.
-
E.
hasOrderOfMagnitudeInJoules
Indicates that the quantity associated with an entity is approximately of a specified order of magnitude when measured in joules.
- 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.