Triple
T25828858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Planck power |
E650604
|
entity |
| Predicate | isNaturalUnitOf |
P153806
|
FINISHED |
| Object | power |
—
|
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: power | Statement: [Planck power, isNaturalUnitOf, power]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNaturalUnitOf Context triple: [Planck power, isNaturalUnitOf, power]
-
A.
isNaturalUnit
Indicates that something is a fundamental, standard unit of measurement defined by natural constants or inherent properties rather than by arbitrary human conventions.
-
B.
isAUnitOf
Indicates that one entity functions as a unit or standard measure in which the other entity is quantified or expressed.
-
C.
usedAsNaturalUnitIn
Indicates that something functions as a standard or reference unit for measuring or quantifying another thing within a natural or intrinsic context.
-
D.
isBaseUnitOf
Indicates that one unit serves as the fundamental reference unit from which another unit in the same measurement system is defined or derived.
-
E.
naturalUnitFor
chosen
Indicates that one entity serves as the standard or most appropriate unit of measurement for quantifying another entity.
- 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_69f6019807f08190bbeb8be744551fdf |
completed | May 2, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 7:37 a.m.