Triple
T2683494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | k_B |
E57427
|
entity |
| Predicate | isFundamentalConstantIn |
P9782
|
FINISHED |
| Object | SI base unit kelvin definition |
—
|
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: SI base unit kelvin definition | Statement: [k_B, isFundamentalConstantIn, SI base unit kelvin definition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFundamentalConstantIn Context triple: [k_B, isFundamentalConstantIn, SI base unit kelvin definition]
-
A.
isFundamental
Indicates that something is a basic, essential, or foundational element upon which other things depend or are built.
-
B.
hasSIUnitForConstant
Indicates that a given constant is associated with a specific SI (International System of Units) unit used to express its value.
-
C.
includesConstant
chosen
Indicates that one entity contains or explicitly references a specific constant value within its definition or structure.
-
D.
isQuantumOf
Indicates that one entity represents a discrete, indivisible unit or packet of the other entity in a quantized relationship.
-
E.
usesConstant
Indicates that one entity makes use of a specific constant value defined or provided by 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_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. |
Created at: March 6, 2026, 9:54 p.m.