Triple
T25828800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Planck density |
E650603
|
entity |
| Predicate | isDerivedFromConstant |
P123741
|
FINISHED |
| Object | Planck constant |
—
|
NE NERFINISHED |
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: Planck constant | Statement: [Planck density, isDerivedFromConstant, Planck constant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDerivedFromConstant Context triple: [Planck density, isDerivedFromConstant, Planck constant]
-
A.
usesConstant
Indicates that one entity makes use of a specific constant value defined or provided by another entity.
-
B.
includesConstant
Indicates that one entity contains or explicitly references a specific constant value within its definition or structure.
-
C.
hasVariantConstant
Indicates that one entity is a specific constant-valued variant or fixed-value form of another entity.
-
D.
hasSIBaseConstantRelation
chosen
Indicates a relationship where something is connected to, derived from, or defined in terms of an SI base constant.
-
E.
variableHeldConstant
Indicates that a particular variable is maintained at a fixed value and not allowed to change while other factors or conditions are varied or analyzed.
- 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_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 22, 2026, 7:37 a.m.