Triple
T9564498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Planck area |
E230755
|
entity |
| Predicate | inPlanckUnits |
P25812
|
FINISHED |
| Object | 1 |
—
|
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 | Statement: [Planck area, inPlanckUnits, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inPlanckUnits Context triple: [Planck area, inPlanckUnits, 1]
-
A.
usesSymbolForReducedPlanckConstant
Indicates that an entity adopts a specific symbol to represent the reduced Planck constant (ħ) in its notation or context.
-
B.
naturalUnitsValue
chosen
Indicates that a quantity is expressed in natural units, specifying its value when fundamental physical constants are normalized (e.g., c = ħ = k_B = 1).
-
C.
symbolForPlanckConstant
Indicates that one entity is the symbolic representation used to denote the Planck constant associated with another entity.
-
D.
baseUnitsInCGS
Indicates that a given physical quantity or measurement is expressed in the base units of the CGS (centimeter–gram–second) unit system.
-
E.
isOfficialSystemOfUnitsFor
Indicates that one system of units is formally recognized or designated as the standard measurement system for a particular domain, region, or context.
- 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_69ca847e53a88190a60eed7e02257f10 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd996a01b081908e2782f41520f73d |
completed | April 1, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69ccd594d0ac8190a81bc11a3a538167 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:04 p.m.