Triple
T2683485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | k_B |
E57427
|
entity |
| Predicate | hasCommonEnergyUnitForm |
P41480
|
FINISHED |
| Object | 8.617333262×10⁻⁵ eV·K⁻¹ |
—
|
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: 8.617333262×10⁻⁵ eV·K⁻¹ | Statement: [k_B, hasCommonEnergyUnitForm, 8.617333262×10⁻⁵ eV·K⁻¹]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommonEnergyUnitForm Context triple: [k_B, hasCommonEnergyUnitForm, 8.617333262×10⁻⁵ eV·K⁻¹]
-
A.
hasUnitOf
Indicates that a quantity, measurement, or value is expressed in terms of a specific unit.
-
B.
standardUnitRelation
Indicates a relationship where one unit is defined, measured, or interpreted in terms of a recognized standard unit.
-
C.
basedUnit
Indicates that one unit is defined in terms of, or derived from, another more fundamental unit.
-
D.
hasEnergyRole
Indicates that one entity plays a specific functional role in the production, distribution, management, or use of energy in relation to another entity.
-
E.
unitOfMeasure
Indicates that one entity specifies the standard unit in which the quantity or value of another entity is measured.
- F. None of above. chosen
Provenance (4 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_69ab4a5028388190a36f3baf1588309e |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd9d7692c81909d8fd9ce3817161b |
completed | March 7, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69abd81c9b4c81908e5e0da6ac5f828b |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd891bcd481909af5340a64ff69f9 |
completed | March 7, 2026, 7:49 a.m. |
Created at: March 6, 2026, 9:54 p.m.