Triple
T6938996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | von Klitzing constant |
E160624
|
entity |
| Predicate | hasCODATAIdentifier |
P74394
|
FINISHED |
| Object | R_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: R_K | Statement: [von Klitzing constant, hasCODATAIdentifier, R_K]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCODATAIdentifier Context triple: [von Klitzing constant, hasCODATAIdentifier, R_K]
-
A.
hasCODATAValue
Indicates that an entity is associated with a value specified or standardized by CODATA (Committee on Data for Science and Technology).
-
B.
CODATA2022StandardUncertainty
Indicates the standard uncertainty value associated with a CODATA 2022 recommended physical constant or measurement result.
-
C.
hasSIUnitForConstant
Indicates that a given constant is associated with a specific SI (International System of Units) unit used to express its value.
-
D.
hasIdentifierSystem
Indicates that an entity is associated with a particular system or scheme used to assign and manage its identifiers.
-
E.
hasSIMBADIdentifier
Indicates that an astronomical object is associated with a specific identifier in the SIMBAD astronomical database.
- 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_69c6884f3db4819080ad65da69386206 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e0c74fe48190aeaa018631e52ef6 |
completed | March 27, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bd5a388190a57a96d925696ff6 |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6e0c620f0819080e0ec49b36d4c30 |
completed | March 27, 2026, 7:55 p.m. |
Created at: March 27, 2026, 2:28 p.m.