Triple
T25828850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Planck power |
E650604
|
entity |
| Predicate | hasOrderOfMagnitude |
P43785
|
FINISHED |
| Object | 10^52 W |
—
|
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: 10^52 W | Statement: [Planck power, hasOrderOfMagnitude, 10^52 W]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrderOfMagnitude Context triple: [Planck power, hasOrderOfMagnitude, 10^52 W]
-
A.
hasMagnitudeProperty
chosen
Indicates that an entity is associated with a quantitative magnitude-related property, such as size, intensity, or amount.
-
B.
isOrderOf
Indicates that one entity specifies the sequence, arrangement, or ranking in which elements of another entity are organized or occur.
-
C.
hasSignificantFigure
Indicates that an entity is associated with a person who plays an important or influential role in relation to it.
-
D.
hasRankOrder
Indicates that one entity is ordered or positioned relative to others according to a specific ranking or sequence.
-
E.
approximateSideLengthOrderOfMagnitude
Indicates that one entity’s side length is approximately the same order of magnitude as another entity’s side length, differing by no more than about a factor of ten.
- 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_69e7ab37438081908f1ccf6284839520 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 22, 2026, 7:37 a.m.