Triple
T7489971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Planck energy |
E176979
|
entity |
| Predicate | approximateNumericalValue |
P9773
|
FINISHED |
| Object | 1.9561 × 10^9 J (CODATA 2018) |
—
|
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: 1.9561 × 10^9 J (CODATA 2018) | Statement: [Planck energy, approximateNumericalValue, 1.9561 × 10^9 J (CODATA 2018)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateNumericalValue Context triple: [Planck energy, approximateNumericalValue, 1.9561 × 10^9 J (CODATA 2018)]
-
A.
hasApproximateValue
chosen
Indicates that one entity’s value is close to, but not exactly equal to, the value of another entity within an acceptable margin of error.
-
B.
hasNumericalValue
Indicates that an entity is associated with a specific numeric quantity or measurement.
-
C.
approximateNumberAwarded
Indicates the estimated quantity of awards or recognitions given in a particular context or event.
-
D.
approximates
Indicates that one entity is close to, but not exactly equal to, the value, form, or behavior of another entity.
-
E.
hasApproximateValueUncertainty
Indicates that the value of something is known only approximately and carries an associated degree or range of uncertainty.
- 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.