Triple
T7489972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Planck energy |
E176979
|
entity |
| Predicate | log10ValueInJoules |
P74388
|
FINISHED |
| Object | about 9.29 |
—
|
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: about 9.29 | Statement: [Planck energy, log10ValueInJoules, about 9.29]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: log10ValueInJoules Context triple: [Planck energy, log10ValueInJoules, about 9.29]
-
A.
outputEnergy
Indicates that an entity produces or releases a certain amount or form of energy as a result of its operation or behavior.
-
B.
relationToWatt
Indicates a relationship that specifies how something is connected or related to Watt, such as by association, reference, or contextual linkage.
-
C.
valueSI
chosen
Indicates that an entity has a quantitative value expressed in SI (International System of Units) units.
-
D.
equalsInAbsorbedDoseTo
Indicates that two entities have the same value or level in terms of absorbed dose (e.g., radiation dose received).
-
E.
logarithmBaseDetermines
Indicates that the chosen base of a logarithm determines how a quantity is expressed or scaled in logarithmic terms.
- 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_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. |
Created at: March 27, 2026, 3:43 p.m.